Hello,
The Better Builds with Maven book says that you can get any element from the
POM with a property like ${project.foo.bar.baz}. Is there a more general
naming convention for properties used by plugins? I see that the
maven-surefire-plugin has configuration elements with these property names:
<parallel> ${parallel}
<printSummary> ${surefire.printSummary}
<redirectTestOutputToFile> ${maven.test.redirectTestOutputToFile}
<remoteRepositories> ${project.pluginArtifactRepositories}
Is there a method to this madness? Is there any "magic" to these properties
like ones starting with ${project...}? I see that one even starts with
${project...} itself. What happens if I have
<project><pluginArtifactRepositories>X</></> and
<plugin><configuration><remoteRepositories>Y</></></>? Then what does
${project.pluginArtifactRepositories} equal?
Thanks,
Paul
--
View this message in context:
http://www.nabble.com/property-naming-convention-tf2413184.html#a6726716
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
