Jochen Wiedmann wrote:
On Jan 11, 2008 10:57 AM, Niall Pemberton <[EMAIL PROTECTED]> wrote:
Theres also the issue of specifying the "version" of the
remote-resources-plugin - which in previous discussions people
objected to. Please Note this is not configuring commons-parent to
*use* that plugin - but just to specify the version number *if* a
component does use it. I don't mind it going in and it has no impact
unless components use it. Does anyone still have a problem with doing
this? Also are there any other changes people think should be made
before trying to release commons-parent-7?
I have no particular problem with it, apart from the fact that I find
it pointless.
If there is some code that actually uses the plugin, then that makes
sense. This code might be contained in some profile, in other words,
not used unless explicitly requested. But just to fix a version
number? What for?
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.
Jochen
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
