Jochen Wiedmann wrote:
On Jan 12, 2008 12:29 AM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
The reason is to have reproducible builds. It makes sure that, no matter
who is building component A, the end result will always be the same.
Specifying versions for all plugins is considered a best practice. This
has been discussed a lot on the Maven mailing-lists. I can give you some
pointers if you like.
Dennis, you don't understand my point. I do not oppose version numbers
in general. I am simply asking to restrict version numbers to those
plugins, which are actually used in a pom file. As soon as the
commons-parent pom *is* using the mrr plugin, then I'm all in favour
for adding a version number.
You don't ask to add a version number for the war plugin, just because
projects *could* use the war plugin, do you?
Yes I would. If one or more of our components was using the war plugin,
then I would ask for the version of the war plugin to be added to the
pluginManagement element in commons-parent.
Jochen
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
