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=36958>. 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=36958 Summary: -noclasspath should be the default Product: Ant Version: unspecified Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: Wrapper scripts AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] I, along with many others it seems, have been hit by the problems that can be caused by having an external CLASSPATH set when invoking ant. In my case, the javac task was ending up with the classpath defined in the javac task, plus the external classpath, which was bugging out the build. This took me a while to track down. I am now aware of the -noclasspath option. I strongly recommend that this be made the default. It will minimize the pain caused to new users. It will help increase portability of build scripts (since it makes the build.xml more self-contained to have any required classpaths defined internally). There are already other mechanisms such as -lib or ~/.ant/lib for including classes just for ant. I'd say just always ignore the external classpath, but you could keep a -useclasspath option if people really need it. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
