Hi JB, Yeah, that probably offers quite a few opportunities to get rid of some obsolete/unnecessary bits in the POMs - we should definitely clean things up as much as possible. I raised https://issues.apache.org/jira/browse/SM-2263 to keep track of this.
Regards, Gert On Mon, Mar 3, 2014 at 4:02 PM, Jean-Baptiste Onofré <[email protected]> wrote: > Hi Gert, > > I agree, but it would also be great to leverage the plugin version from the > Apache POM (and avoid to override the version in our POMs). > > Anyway, it's something that we can do in two parts: > - upgrade to Apache POM 13 first > - cleanup the plugin/dependency management > > Regards > JB > > > On 03/03/2014 03:30 PM, Gert Vanthienen wrote: >> >> L.S., >> >> >> The parent POM for our ServiceMix 5 build currently is our own >> servicemix-pom, version 5. How about switching over to using the >> apache-13 POM directly? That one now has all the release/deploy setup >> we used to have in our own parent POM, so the only bits we would have >> to the ServiceMix 5 root POM would be things like issueManagement and >> probably the mailing list information. >> >> >> Regards, >> >> Gert Vanthienen >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
