DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28034>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28034
The javacc target is practically useless as implemented
Summary: The javacc target is practically useless as implemented
Product: Ant
Version: 1.5.4
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: Core tasks
AssignedTo: dev@ant.apache.org
ReportedBy: karltk@gentoo.org
The current javacc target, as implemented in
src/main/org/apache/tools/ant/taskdefs/optional/javacc/JavaCC.java is no longer
useful.
The ant documentation (http://ant.apache.org/manual/OptionalTasks/javacc.html)
for this target refers to the http://javacc.dev.java.net home page, which does
not offer any suitable JavaCC.zip.
In fact, the supplied binaries and sources for the 3.2 version (the only version
available), build to a completely regular javacc.jar file, which can easily be
added to the classpath, rendering the convoluted hoop-jumping with JavaCC.zip
obsolete.
Is there any way that the current insanity can be dropped completely, in favour
of perhaps an internal check of available classes to determine if the javacc
class is present in the classpath?
Alternatively, can the documentation on the web about the JavaCC target be
updated with a description of how to make the current target work with the
binaries and sources for javacc 3.2, which indeed are referred to by the
http://javacc.dev.java.net link?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
|