I think this is a great idea. You could even put the new apache wide repository and staging area in the release profile. Would make doing a release a snap IMO.
Martijn On Tue, Apr 14, 2009 at 9:18 PM, Brian Fox <[email protected]> wrote: > 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? > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
