|
||||||||||||
|
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)

What makes you believe that it is the usage of the Ant task rather than direct call to JarSigner which is responsible for most of the performance impact? Have you run a profiler on it? My understanding is that signing a JAR is simply slow using whatever tool, due to the cryptographic work.