[ http://jira.codehaus.org/browse/MOJO-396?page=comments#action_65326 ]
Holger Brands commented on MOJO-396: ------------------------------------ some more information is available here: http://weblogs.java.net/blog/kirillcool/archive/2005/05/signing_jars_fo.html we're using this mechanism a long time without problems. I agree, it requires some effort to implement this in the plugin. Perhaps there could be a way to mark a dependency as already signed and point to a component extension JNLP in src/jnlp ... The plugin could then skip signing and instead reference this JNLP from the main JNLP. Just some thoughts ... > support component extension mecanism for already signed jars > ------------------------------------------------------------ > > Key: MOJO-396 > URL: http://jira.codehaus.org/browse/MOJO-396 > Project: Mojo > Type: New Feature > Components: webstart > Reporter: Jerome Lacoste > > > Spawned from: http://jira.codehaus.org/browse/MOJO-263#action_65228 > MOJO-263, support unsigning jars, was created to deal with jars that have > been already signed. > 1- it is not the only way to deal with already solved jars. One can use the > component extension mechansim outlined here: > > http://java.sun.com/j2se/1.5.0/docs/guide/javaws/developersguide/faq.html#213 > 2- unsigning may not be allowed on some jars (can someone double check this?) > My understanding is that there are some cases were component extension didn't > work (implementation issues). It may also be that this feature is harder to > implement. > So we may want to also support both features. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
