Re: Master pom and plugin versions

[Johan Lindquist]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Something else to consider - should the 'defaults' currently defined in
the plugins section be move to the pluginManagement section?  That way,
plugins are not necessarily enabled by default in the child-poms but
they can choose to override the settings if enabled.

Cheers,

Johan


Niclas Hedhman wrote:
> On Sat, Jan 23, 2010 at 6:33 AM, Johan Lindquist <jo...@kawoo.co.uk> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
> 
>> Have vague memories about a mail a while ago about pinning the plugin
>> versions used by the mater pom.  Not a bad idea in my opinion - any
>> objections against me doing this in the next version of the pom (which i
>> am fixing to sort out the checkstyle and site version changes already)?
> 
> That is probably a good idea.
> There is a general tendency that rebuilding an old project that didn't
> nail down the versions of everything is troublesome at best, and
> outright impossible at worst. Having all plugins nailed down version
> wise seems like a safe bet for future compatibility.
> Downside, more versions to maintain, but perhaps the master pom
> approach is good enough to make this less of a concern.
> 
> Alin?
> 
> 
> Cheers

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAktdnf0ACgkQpHYnED7evipJkgCeKZ8Q6Jk2ywNoPKtSYqGj4Hxm
Vw4An0DSYxWYg+dYp4pcr6GSLOEBAUJK
=n7a/
-----END PGP SIGNATURE-----

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general