https://bz.apache.org/bugzilla/show_bug.cgi?id=58404
--- Comment #2 from Sebb <s...@apache.org> --- (In reply to Christopher Schultz from comment #1) > This may not be a bug: ant scripts often provide sane defaults in case the > properties files do not specify a value: See Bug 58083 - the same issue was fixed in Tomcat itself. > it's possible to remove > compile.source for example from build.properties.default and end up > confusing the compiler. build.properties.default is not supposed to be changed. > Note that ant does not allow property values to be changed once they have > been set, so the value from build.properties.default will override the > default hard-coded in build.xml. This is partly why it's a bad idea; the user may change the value in build.xml and wonder why the change has no effect. But the main issue is that it's not a good idea to have multiple definitions of the same data. At least one definition is likely to get out of date. viz JUnit. Either define the values in the properties file or in build.xml; don't define them in both. But I think the properties file is better for these properties; it's easier to read and maintain. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
