On Thu, 2014-01-16 at 16:43 +0000, sebb wrote: ...
> > However, looking at the gradle wrapper I cannot work out how to easily > test signing without going through most of the release process. > Artifact signing is still done by Maven. The script merely starts Maven as a separate process. I could replace this task with Gradle but as far as I know it still does not support GPG integration, so signing credentials need to be sourced from a property file. I am not sure what is the best way froward here. Oleg > With Maven, it's trivial; just change to a valid project workspace and run: > > mvn package -DskipTests gpg:sign -Dgpg.keyname=xxx > or > mvn package -DskipTests gpg:sign -Pkeyprofile > > where the keyprofile includes the keyname (and potentially the > gpg.secretKeyring location) and is stored in settings.xml > > > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
