-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jörg Schaible wrote: > Johan Lindquist wrote at Montag, 25. Januar 2010 14:34: > > 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. > >> Remember that the pluginManagement is unfortunately not applied to the >> plugins used in the report section. To pin the report plugins, you have to >> set the version every time you are using it (although you can inherit the >> version from a report plugin defined in the parent(s)) :-/
Yes, have noticed this - currently approaching it as you suggest, pinning the reports that were already enabled in the root pom - but indeed, child projects need to pin the versions of any other reports they enable. Currently pinned reports in the master pom are: - - javadoc - - project info reports - - jxr - - cobertura - - checkstyle - - surefire >> - Jörg > > 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 > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general - -- you too? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktd/KEACgkQpHYnED7eviphzACfcaomhNcFTWi8AGwyfzKKQ0v/ AZQAoKauw4FBe5wcrszf2Ey9M/Su3jts =ZWAh -----END PGP SIGNATURE----- _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
