[
https://jira.codehaus.org/browse/MNBMODULE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=299067#comment-299067
]
Pino Silvaggio commented on MNBMODULE-140:
------------------------------------------
We have a situation where we need to include some files, like icons and
application server descriptors, but the nbm plugin doesn't have this
flexibility. Therefore we wanted to sign the webapp by ourselves, so I patched
the plugin and added a "sign" parameter (true or false) but that did not work
so well, for some reason there was some instability with the platform loading
resources...
I was generating the webapp unsigned and then used the jarsigner plugin to
force unsigning and timestamping (which nbm doesn't support). Plus, I was
adding src/main/webapp resources.
As I said, my experience with this scheme wasn't good.
> NBM plugin should allow not signing jars when generating webstart binaries
> --------------------------------------------------------------------------
>
> Key: MNBMODULE-140
> URL: https://jira.codehaus.org/browse/MNBMODULE-140
> Project: Maven NetBeans Module Plugin
> Issue Type: Improvement
> Affects Versions: 3.5
> Reporter: Tomasz Bartczak
> Assignee: Jesse Glick
>
> In webstart-app goal nbm plugin is signing all jars that will go into war
> package.
> There should be an option in configuration
> <signJar>true|false</signJar>
> Like in harness there was an option that was accepted by build system:
> jnlp.sign.jars=false
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
