On 6/3/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On 6/2/06, Paul Fremantle <[EMAIL PROTECTED]> wrote: > I like the idea of automation. > > What would be even more helpful would be a default Apache project > setup, with a maven release target that builds a release in the right > format. > > If the project structure started out with LICENSE, NOTICE, JAR targets > that put those in META-INF, places to put auxiliary licenses, etc, and > produced signatures, MD5s, etc from day 1, then podlings would be off > to a great start.
incubator release codification has been my TODO list for quite a while now. still working on the release signing documentation ATM but there seems to be quite a bit of momentum on this now. a project structure would be a good start for this documentation. one of the issue i find difficult is balancing autonomy with good practice. the actual policy requirements are actually pretty small. however, there are quite a lot of additional material which falls under best practice which is (by nature) a little subjective. i think that a list of best practice and a base structure would be useful as a menu from which podlings could bootstrap their own standards.
Also seems like a easier first step than validation. > I proposed a patch for m2 that would allow LICENSE and NOTICE files to automatically be included in the jar files (MJAR-42) - I've not had any feedback on it yet. The structure thing sounds like an Apache-specific archetype mojo - how about we start a small project here to kick it off (potentially moving it to m2 later)?
we've talked about this before over in jakartaland. a tool would be most useful if it encorporated elements of best practice (for example, good MANIFESTS) as well as the minimal requires for an ASF release. probably best to pool resources. - robert
