I 've encountered this problem in the m1 plugin with acegisecurity.org.
Basically, just add a dependency to 0.9.0 (its in ibiblio and signed by Ben Alex the lead of acegi) and see what happens when you build it and try it out in webstart. The webstart plugin in m1 couldn't handle it, because the jar's manifest was single signed but there were 2 signatures in the META-INF (or the other way around), so the jnlp didn't work in webstart 1.5.
I ended up creating a 0.9.0.unsigned version of acegi. jerome lacoste wrote:
Hi all, One of the last thing I want to fix before making the m2 webstart plugin beta is related to signing jars that are already signed. I haven't had to face the issue yet, but it seems that there's a potential issue when dealing with including such dependencies in a webstart application. In particular see: http://jira.codehaus.org/browse/MOJO-7#action_49160 and the relevant m1 jnlp issues: http://jira.codehaus.org/browse/MPJNLP-20 http://jira.codehaus.org/browse/MPJNLP-28 I would appreciate feedback (and better: test cases) to avoid releasing an m2 plugin that doesn't solve these problems. Cheers, Jerome
-- With kind regards, Geoffrey De Smet --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
