On 13/05/2010, Oleg Kalnichevski <[email protected]> wrote: > On Thu, 2010-05-13 at 17:55 +0100, sebb wrote: > > On 13/05/2010, ant elder <[email protected]> wrote: > > > On Thu, May 13, 2010 at 4:49 PM, sebb <[email protected]> wrote: > > > > > > > > > > > > > > This is actually quite easy, see > > > > https://issues.apache.org/jira/browse/COMMONSSITE-55 > > > > > > > > > > > > > Thanks for the pointer, i didn't know you could do use a file url in > > > altDeploymentRepository. > > > > > > > BTW, you can also add the profile to your local settings.xml. > > > > Though if many people may want to use the same method, it is more > > efficient to add it to a shared resource such a a parent pom. > > > > > This approach results in corrupt / inconsistent maven metadata > (maven-metadata.xml) unless the metadata is manually copied over. >
This is what the Apache Nexus repo is for, see: http://maven.apache.org/developers/release/apache-release.html [As far as I can tell, one can use deploy to upload to the repo if one does not use the release plugin.] PMC then votes on the repo contents, which are then either promoted or dropped. == Note that I raised the issue of whether Maven sources need to be voted on with the board/infrastructure. All the responses say that Maven source packages need to be voted on by the PMC, and this is supported by the updated releases FAQ at: http://www.apache.org/dev/release.html This also requires jars etc. to have N&L files, which implies that the Maven artifacts also need to be reviewed. Voting on source releases is not an issue that is decided by PMCs; it is mandated by the ASF. > Oleg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
