> The maven release process criticism from Dan Kulp spawned an impromptu > ApacheCon gathering of the minds (Dan Kulp, Wendy Smoak, Jason Van Zyl, > and Myself) to define a better release process for maven.
First off, thanks for that discussion. It was nice to sit down and really spell out the issues and brainstorm on solutions. > * license:check > Using the same filetype list as license:inject, this will create a > build-time failure if the > license does not exist in one or more files in your project tree. I'd like to also see a maven reports version of Roberts ARAT tool. If Robert is going to run that on all the incubator releases, it would be nice if a maven plugin could do it automatically and add it to the site reports. > The top level apache.pom will also define the -sources.jar and > -javadoc.jar creation with appropriate LICENSE file injection as well. Out of curiosity: is adding the LICENSE to the javadoc or sources jars even possible at all right now? I'm not really seeing anything in the docs for either of the two plugins. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 F:781-902-8001 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
