On 27 Feb 07, at 2:48 PM 27 Feb 07, Daniel Kulp wrote:
On Tuesday 27 February 2007 14:27, Jason van Zyl wrote:
On 27 Feb 07, at 12:57 PM 27 Feb 07, Daniel Kulp wrote:
I'm working on fixing the issues in the gpg plugin. I just
committed some
changes but would like a bit of discussion before finalizing some
of it.
MGPG-2 - Allow the selection of a particular signature
I added a keyname parameter (-Dkeyname=foo) etc... which can be
used. It
maps directly to the gpg --local-user flag. That should solve
that one.
Something we're trying to practice is namespace usage in parameters
so use
-Dgpg.keyname
So that other plugins that might use "keyname" can do the same and
not cause a collision.
Should the passphrase change to -Dgpg.passphrase to match?
I thought it already was.
That would
break your release instructions when we go to the newer version of
the gpg
plugin. Not sure if that's a huge deal as it would require moving
to a
new parent pom anyway.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog
---------------------------------------------------------------------
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]
