https://issues.apache.org/bugzilla/show_bug.cgi?id=49918
Jesse Glick <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #4 from Jesse Glick <[email protected]> 2010-09-21 09:10:52 EDT --- (In reply to comment #2) > It seems that the default value for the includeantruntime > parameter was reversed No, it was not. It was, and remains, "true" - which is bad, since it is nonportable, but not something we can change without breaking some existing scripts (e.g. causing previously successful runs of <javac> to fail with compiler errors). > This action caused 100s of my own build.xml files > to now require editing in order to avoid this warning Sorry, but they should have been edited before now to specify includeantruntime="false" anyway. The warning is just reminding you to do this. Note that you can also use macro or presetdef to define common settings for <javac> in your scripts. You may also define the magic property build.sysclasspath=ignore to effectively change the default for Ant - in a master script using <property>, in ~/.antrc, etc. - if you are sure you have no instances of <javac> which are relying on the old default. (For cases where you do want to compile an Ant task, it is best to add <pathelement location="${ant.core.lib}"/> to the appropriate <classpath>.) Again, please read the thread on the dev list and post comments there. Nobody likes the current state, but issuing some warnings and continuing is considered a lower-priority incompatibility than causing a build to fail, even if the warnings affect more scripts than would have been broken by a change in defaults. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
