On 19 April 2011 15:00, Mark Thomas <ma...@apache.org> wrote: > On 18/04/2011 22:40, sebb wrote: >> As suggested by Hen, we should be able to use lazy consensus voting >> for Commons Parent pom releases. >> >> [ ] +1 let's use lazy consensus voting for Commons Parent pom in future >> [X] -1 why not? > > It is a release and that requires a positive action from the PMC to > approve the release to ensure the necessary legal protection for the > release manager is in place. > > It appears that Commons Parent is released to Maven central but not to > the standard ASF /dist location. That needs to be corrected. All > releases must be released via the standard ASF /dist location to ensure > that releases are correctly archived. > > That Commons parent is only intended for use as a dependency by other > Commons components is irrelevant. It is released therefore the standard > rules regarding releases must be adhered to.
It is part of the build process, and is not part of the source. In theory, users can still build the code by hand from the source archive (but it would be hard work in some cases to establish the dependencies). In some cases, it is not even needed to build the source, as some components also have Ant builds. Note that Maven core is released to /dist, however AFAICT none of the plugins are released to /dist, nor is the Apache Parent Pom. So even if Commons uploads the parent pom, it won't be possible to use it without relying on Maven Central. I suspect other projects that use parent POMs may also not be publishing these to /dist. It would be fairly easy to add the Parent Pom to /dist, but personally I cannot see the point unless all the required dependencies are also released via /dist as well. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
