L.S., Here's my +1 as well.
FWIW, this pom already builds fine with Maven 3 without any warnings on my machine. I was even tempted to do the actual release with Maven 3, but I sticked to Maven 2.2.1 for that. Personally, I don't use the deploy.altRepository but I kept it in because some people don't like doing the remote deploy during the release build but prefer to upload the staging bits afterwards. Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Fri, Oct 29, 2010 at 10:52 AM, Jean-Baptiste Onofré <[email protected]> wrote: > +1 > > Anyway, maybe we could begin to add changes required by Maven 3, such as > defining the plugin version number to avoid Maven 3 warnings. > It's the case for the maven-release-plugin and maven-deploy-plugin version. > Another thing is about the deploy.altRepository property. I don't know if > some of you use it but it isn't required now as we use Nexus. > Anyway, these changes could be postponed to servicemix-pom 6. > > Regards > JB > > On 10/29/2010 10:42 AM, Gert Vanthienen wrote: >> >> L.S., >> >> The new parent pom under vote includes the changes: >> - an update to the latest apache parent pom (version 7) >> - a few optional Maven repositories have been removed >> - a few updates to the developer information section >> >> The staging repo for this release is at >> >> https://repository.apache.org/content/repositories/orgapacheservicemix-001/ >> The tag for this release is >> >> http://svn.apache.org/repos/asf/servicemix/servicemix-pom/tags/servicemix-pom-5/ >> >> Thanks for taking the time to review and vote! >> >> Gert Vanthienen >> ------------------------ >> FuseSource >> Web: http://fusesource.com >> Blog: http://gertvanthienen.blogspot.com/ >
