... more background info, trying to be more accurate and complete this time, if anyone sees anything that should be clarified, please jump in ...
antrun is able to see property value changes during an <execution> run because of two things: * it is manually pulling xml out of its own configuration section [1], and resolving the expressions it each time it comes across them during ant execution * during the run, the properties are ant properties (initialized with corresponding maven property values), and don't get written back to maven properties unless you explicitly do so [2] other plugins typically wouldn't be doing this, and instead rely on whatever is passed in from the container, the stuff passed in from the container is whatever is seen in help:effective-pom (things explicitly declared in configuration sections) plus resolutions of default values (if the default values contain expressions, they are evaluated right before the plugin runs) [1] http://svn.apache.org/viewvc/maven/plugins/trunk/maven-antrun-plugin/src/main/java/org/apache/maven/plugin/antrun/AntRunMojo.java?view=markup (line 457 is a interesting spot) [2] http://maven.40175.n5.nabble.com/Exporting-Ant-properties-to-Maven-td510023.html#a510117 -- View this message in context: http://maven.40175.n5.nabble.com/Shuttling-Property-Values-between-Maven-and-Ant-tp2641670p2642018.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
