On 1 Sep 06, at 4:26 AM 1 Sep 06, Jochen Wiedmann wrote:
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.
We talked about it on the list and there was well longer then 72
hours this time. The prefix is for command line use and I asked if
the new standard could be used and folks agreed.
"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
I'd like to see the logic worked out for all things i.e. what if you
didn't want the JARs in a module recreated but you added something
other then a JAR to an assembly and you wanted that recreated.
We start with the concrete and move the general.
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?
If you want to work out a parameter that covers everything then write
something up. I'm not sure it's as simple as you think. I would think
there would be instances where you might want a mix and one parameter
isn't going to cover it. Write it up and let folks look at it.
At any rate I annotated the commit, then posted to the list about the
change, and gave probably 144h before I released it.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Jason van Zyl
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
