2 * +1 -- Olivier
2009/4/21 Brian Fox <bri...@infinity.nu>: > Time to release the updated parent poms: > > https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom > > https://repository.apache.org/content/repositories/maven-staging-012/org/apache/maven/maven-parent/12/maven-parent-12.pom > > The changes were described in a previous thread: > "We currently have some expectations about what artifacts are created for > apache builds, such as javadocs and source jars, and specifically artifact > signatures. Currently each project must configure the current release > profile in their own top level pom. This raises the bar of entry for new > projects and creates more work for us to help them get it sorted out. > > I'd like to take the maven release profile and release plugin config and > push it up to the apache pom to make it consistent and easy for all apache > projects to produce proper releases. I think to do it and avoid conflicts > with any existing profiles, I would change the profile name from "release" > to "apache-release" and activate that by default. Does anyone see any > downsides to this?" > > In addition to moving the profile, I pulled up the pluginManagement and the > default source encoding. I think if these things are best practices for the > Maven project, they can be default best practices for any Apache project as > well. > > Vote is open for 72hrs: > > +1 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
