|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MNBMODULE-179) Archetype for IDE plu... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-179) Archetype for ID... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-179) Archetype for ID... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-179) Archetype for ID... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-179) Archetype for ID... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-179) Archetype for ID... Jesse Glick (JIRA)

Also MNBMODULE-151 would be useful since PP issues a warning if the NBM is unsigned, and possibly does not even let you request verification of it. So ideally the archetype would preconfigure the plugin to sign all modules; when first run you would get a warning that there is no signature info (keystore, storepass, alias), with instructions to either point to an existing keystore if you have one, or offering a CLI goal to generate and use a new one.