|
||||||||
|
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-204) Use JarSigner clas... Seb Calbaza (JIRA)
- [mojo-dev] [jira] (MNBMODULE-204) Use JarSigner... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-204) Use JarSigner... Seb Calbaza (JIRA)
- [mojo-dev] [jira] (MNBMODULE-204) Use JarSigner... Seb Calbaza (JIRA)
- [mojo-dev] [jira] (MNBMODULE-204) Use JarSigner... Seb Calbaza (JIRA)
- [mojo-dev] [jira] (MNBMODULE-204) Use JarSigner... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-204) Use JarSigner... Seb Calbaza (JIRA)
- [mojo-dev] [jira] (MNBMODULE-204) Use JarSigner... Pino Silvaggio (JIRA)
- [mojo-dev] [jira] (MNBMODULE-204) Use JarSigner... Pino Silvaggio (JIRA)

Yes, it's part of the JDK as is the jarsigner executable and other tools, so shouldn't be an issue using it.
Also the license is GPL whit Classpath Exception and from my understanding it's ok to be directly used (linking against it).
Don't think the interface changed from JDK 1.5... so I think there is no real reason that it will change in next releases... and even if it changes I see no issue with it.
I made this change because I did not wanted to wait 30 min for a webstart build as I'm in the development phase and need to quickly ship changes .... changing it reduced the build to just under 1 min.