Thanks! To summarize:
Tell assemblies to "attach" - so the gpg plugin will do the code signing. Block the default deploy step. Use the Wagon plugin to deploy things. 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? -Marshall On 11/4/2010 3:46 PM, Antonio Petrelli wrote: > 2010/11/4 Marshall Schor <[email protected]>: >> Now, we are trying to better align with the Maven way, and are using Nexus. >> The >> default for assemblies will attach these 16 mb things as artifacts of the >> aggregation project, and mvn release:perform will put them into the Nexus >> repository. >> ... >> Is this OK for these big assemblies (both binary and source)? I would also >> copy >> these to the Apache distribution spot, to have them automatically mirrored, >> in >> addition. Is this the right approach? > IMHO deploying assemblies in a Maven repository is entirely optional, > since other developers rarely take these artifacts as a dependency. > IOW, do it if you need it. > >> I experimented with marking the binary assembly with the configuration >> <attach>false</attach> - this works, and prevents it from going up to Nexus >> (and >> then on to Maven central), but has the bad side effect of preventing the >> maven-gpg-plugin from signing that artifact. This is because the maven gpg >> plugin only signs "attached" artifacts. > There's another way, that I use with Tiles and Velocity: skip the deploy > http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#skip > and, in the deploy phase, I use Wagon plugin, with some tricks > (install signatures in local repository, copy from local repository > installed artifacts to target folder), to upload assemblies to their > final place. > You can see it working here: > http://svn.eu.apache.org/repos/asf/tiles/framework/trunk/assembly/pom.xml > See the "apache-release" profile. > > HTH > 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]
