Hi,
I just noticed that the jar plugin uses the property
${jar.forceCreation} as default of the new parameter "forceCreation". I
find this choice most unfortunate.
"Forcing creation" is a very general concept: Almost any plugin could
use it, including compiler, assembly, war, ear, ejb, javadoc, ... If any
such plugin will end using a different property for the same thing, then
it will be almost impossible to do a "forced creation" on the whole
project. Also note, that it is not required to have this property "per
plugin": For example, if I want to rebuild just the jar file, then I can
do so by running
mvn -Djar.forceCreation=true jar:jar
mvn install
IMO, a much better choice would be "maven.forceCreation", or whatever.
Is it too late for that?
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
