Hi Marshall,
thanks a lot for your hints, very appreciated!
Have a nice day,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Sep 10, 2010 at 9:41 PM, Marshall Schor wrote:
> Another approach is to install a version of the underlying gpg which includes
> support fo
Another approach is to install a version of the underlying gpg which includes
support for an agent.
Then, when gpg needs to get your pass phrase, it asks the agent. The agent pops
up an interactive window, and gets your pass phrase, right when it needs it. It
then keeps it around for a few minu
Hi Kalle,
thanks a lot for your help, very appreciated.
Have a nice day,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Sep 10, 2010 at 7:06 PM, Kalle Korhonen
wrote:
> You need to specify:
> forked-path
> in release plugin configuration. See http://jira.codehaus.
You need to specify:
forked-path
in release plugin configuration. See http://jira.codehaus.org/browse/MGPG-9
Kalle
On Fri, Sep 10, 2010 at 9:30 AM, Simone Tripodi
wrote:
> Hi all guys,
> using the maven-release-plugin and signing artifacts with GnuPG,
> during the verifying phase, when the gpg-
Hi all guys,
using the maven-release-plugin and signing artifacts with GnuPG,
during the verifying phase, when the gpg-plugin is invoked, the build
process is completely stalled. If I don't pass the gpg.passphare I'd
expect it would be asked in the prompt, but it doesn't happen :(
Follow below my a
