Thanks Brian and Jason for your thoughts. They were a big help.
I think I have it mostly worked out now, just committed the changes.
1) Added a gpg.skip to skip the signing. Mostly useful for --batch-mode
2) If running in batch-mode and no passphrase is available, throw a
MojoExecutionExce
>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.
Just a thought, does it make sense to modify the core to automatically
prepend the plugin name to the fr
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
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 - All
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
1) It seems logical to only ask once per pom at a minimum. The
multimodule issue would probably have to wait until the plugin shared
context is flushed out.
2) I would say it should fail by default, but you could make a parameter
to allow someone to configure it to just skip if no password is
avail
