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 available.
-----Original Message----- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 27, 2007 12:58 PM To: Maven Developers List Subject: gpg plugin questions The questions I have are: 1) Is allowing GPG to ask for the passphrase for every artifact acceptable? If not, we'll need to ask ahead of time and cache it. However, what happens in multi-module builds? Where can we store it so we don't have to ask again? (I suppose we could abuse System.setProperty(...) or something. Ick.) 2) The comment on MGPG-1 says "the plugin should detect that Maven is running in batch mode, and not prompt in that case". In that case, what's supposed to happen? gpg really needs a passphrase. Should it fail? Should it just not sign anything? Thanks! -- 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]
