It was me, and my point is that if you *must* keep them in sync in more than one location, the lesser evil is a property.
This is usually when you have a suite of dependencies and you want to ensure the same version is used for all... but it is equally valid between dependencies and plugins and between plugins and reporting plugins. And I am not saying using properties is not evil, just the lesser evil ;-) On 29 January 2013 14:12, Anders Hammar <[email protected]> wrote: > Right, I'm not to fond of using properties but there was a recent thread > on the users list where Stephen (I think) suggested/argued this approach in > these cases. I guess in this case history has shown the problem of NOT > using a property to keep them in sync. > > In any case, we should keep these plugins versions in sync. With or > without a property. > > /Anders > > > On Tue, Jan 29, 2013 at 2:54 PM, Tony Chemit <[email protected]> wrote: > >> On Tue, 29 Jan 2013 13:38:50 +0100 >> Anders Hammar <[email protected]> wrote: >> >> > -0 >> > >> > The versions of the surefire plugins aren't aligned. The reporting >> plugin >> > is still on 2.12.4 but the m-surefire-p is on 2.13. We should probably >> use >> > a property for this one. >> >> Arch i tried to do this some time ago and someone (you?) told me it is >> not good :( >> >> Do you remember of >> https://jira.codehaus.org/browse/MOJO-1851?focusedCommentId=301689&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-301689;) >> >> That's why I would like to do this for every plugin acting as a report >> too. >> >> So now I am a bit confused, don't know what to do (when to use a property >> and when not). >> >> >> -- >> Tony Chemit >> -------------------- >> tél: +33 (0) 2 40 50 29 28 >> email: [email protected] >> http://www.codelutin.com >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> >
