Cool - thanks for explaining Dan and JB. +1 from me on the new parent pom.
David On 3 July 2014 14:19, Jean-Baptiste Onofré <[email protected]> wrote: > Hi, > > I second Dan here: it's exactly the purpose of the new parent pom: simplify > modules pom, gather/align the dependencies (and plugins dependency), etc. > > Regards > JB > > > > On 07/03/2014 02:59 PM, Daniel Kulp wrote: >> >> >> On Jul 3, 2014, at 7:51 AM, David Bosschaert <[email protected]> >> wrote: >> >>> Again, as with the other batches I would only feel comfortable voting >>> on this if there was some indication around what has changed. Would >>> you be able to provide this please? >> >> >> Well, the new parent is a huge change. We previously had separate java5 >> and java6 parents. Much of the configuration for things like the versioning >> plugin were NOT in the parent and forced to be in every pom, etc… This >> release pretty much collapses the old “parent” hierarchy down to a single >> pom and configures as much as we can in there so that the other modules poms >> can be smaller have less cruft. >> >> Dan >> >> >> >>> >>> Thanks, >>> >>> David >>> >>> On 30 June 2014 19:10, Guillaume Nodet <[email protected]> wrote: >>>> >>>> This is the first release of a set. >>>> It contains the parent pom in version 2.0.0 >>>> >>>> Staging repository available at >>>> https://repository.apache.org/content/repositories/orgapachearies-1002 >>>> >>>> [ ] +1 Release parent 2.0.0 >>>> [ ] -1 Do not >>>> >>>> Cheers, >>>> Guillaume Nodet >> >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
