maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse McConnell <>
Subject Re: Improving the apache parent pom
Date Tue, 14 Apr 2009 19:20:26 GMT
I think it is a fine idea and would serve as a good example of best
practices for other organizations to follow...


jesse mcconnell

On Tue, Apr 14, 2009 at 14:18, Brian Fox <> 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:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message