Hi guys, I like small and simple parent poms, but they should perform a few functions that some developers may not think about...
Just a few things that I'm thinking of: 1. API versioning baseline checks 2. Legal checks (typically done by the rat-maven-plugin) 3. Have the correct settings to do releases 4. By default don't export any packages Looking at your parent pom, I see that you already have points 1, 3 and 4 covered. Not sure if point 2 is there right now... In general +1 to your effort! Cheers, David On 12 April 2016 at 10:14, Jean-Baptiste Onofré <[email protected]> wrote: > +1 (as discussed yesterday) > > Regards > JB > > > On 04/12/2016 11:02 AM, Christian Schneider wrote: > >> I think it is pretty hard to work with the current Aries parent pom. >> https://github.com/apache/aries/blob/trunk/parent/pom.xml >> >> My main issue with it is the very special definitions for the >> maven-bundle-plugin. It is difficult to set up a project and it is very >> easy to >> end up with a broken Manifest. >> >> So for aries-rsa I created a new parent pom and just took the necessary >> minimum from the aries parent. >> https://github.com/apache/aries-rsa/blob/master/parent/pom.xml >> >> Especially for the maven-bundle-plugin I used the approach to leave the >> parent at defaults. I also used the include to be able to extract the >> bundle config in a separate bnd file. >> This resulted in very small poms as well as bnd.bnd files in the >> individual projects. >> e.g.: >> https://github.com/apache/aries-rsa/tree/master/topology-manager >> >> So I would like to discuss to create a new parent pom for aries (like >> 3.0.0-SNAPSHOT). The main thing would be to use similar >> maven-bundle-plugin settings like above but we could also revisit the >> other >> plugins to see if we can make them simpler. >> >> Christian >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
