I've thought more about this, and after exploring a bunch of different paths, I'm thinking of this process for my big assemblies:
Have the release process produce the assemblies as "attached" artifacts (so that the maven-gpg-plugin will do the signing). Let the normal release "deploy" happen for these assemblies - this will upload them (with checksums added) to the Nexus "staging" area. Although the assemblies are large, they will then be in a spot where other developers on the project can download them (with or without maven) and test the release. If these assemblies were not put there, they would need to take up space somewhere else in the Apache infrastructure for sharing with the development community for testing, anyways. After a successful release vote, use the Nexus GUI to delete these assemblies, before pushing the "release" button. This prevents them from going up to Maven Central. And, of course, copy the assemblies you want to have mirrored by the normal Apache distribution mechanism, to the spot for your project. This seems to require the least special maven POM code (essentially, none, I think - so that might qualify it as a maven best practice :-) ). Does anyone see a flaw in this approach? -Marshall Schor On 11/4/2010 5:06 PM, Antonio Petrelli wrote: > 2010/11/4 Marshall Schor <[email protected]>: >> On 11/4/2010 4:21 PM, Antonio Petrelli wrote: >>> 2010/11/4 Marshall Schor <[email protected]>: >>>> I not sure why you did the ant task to select/copy/rename some things - >>>> was that >>>> because you couldn't get the names right in the first place, or the wagon >>>> couldn't be configured to deploy just what you wanted? >>> For renaming artifacts and to copy digests that otherwise are not >>> accessible. >>> Remember to activate this: >>> http://maven.apache.org/plugins/maven-install-plugin/install-mojo.html#createChecksum >> Just checking my understanding: >> >> The normal deploy operation (which here we've disabled by saying >> <skip>true</skip>) adds checksums when uploading to a repository. >> >> The Wagon upload goal doesn't do this. >> >> The install plugin (which installs to your local repo) normally (by default) >> doesn't do checksums. The solution to get the Wagon goal to upload things >> with >> checksums, is as follows: >> >> 1) First have the install phase run, with an override configuration to >> generate >> the checksums. This results in your local .m2 repo having the checksums. >> 2) Configure the Wagon plugin to upload from the local repo spot, and run >> after >> the "install" phase. > Check passed :-D > > Antonio > > --------------------------------------------------------------------- > 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]
