By default, the gpg plugin signs only attached artifacts, so (assuming that it's GPG output you are talking about, or if not a similar plugin) you'll have to add manual configuration, yes, to sign those additional files. The assembly plugin is blissfully ignorant of the entire process.
On Sat, Feb 25, 2012 at 4:24 PM, Simone Tripodi <simonetrip...@apache.org> wrote: > Hi all guys, > > I configured the assembly-plugin to prevent generated artifacts are > attached, so they won't be deployed on Nexus, but I still need the > checksums are generated for that artifacts. > Is there a way to do it or I have to use the external checksum-plugin? > TIA, > -Simo > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
