Re: Improving the apache parent pom

2009-04-14 Thread Brian Fox
Martijn Dashorst wrote: 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. That part is already in Apache-5 ;-) ---

Re: Improving the apache parent pom

2009-04-14 Thread Martijn Dashorst
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 wrote: > We currently have some expectations about what artifacts are created for > a

Re: Improving the apache parent pom

2009-04-14 Thread Jesse McConnell
I think it is a fine idea and would serve as a good example of best practices for other organizations to follow... jesse -- jesse mcconnell jesse.mcconn...@gmail.com On Tue, Apr 14, 2009 at 14:18, Brian Fox wrote: > We currently have some expectations about what artifacts are created for > ap

Improving the apache parent pom

2009-04-14 Thread Brian Fox
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 proj