[
http://jira.codehaus.org/browse/MWEBSTART-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chad Lyon closed MWEBSTART-110.
-------------------------------
Resolution: Won't Fix
Ooops, I had never tried using this plugin with packaging=pom. This
accomplishes exactly what I want. This is not actually a bug. I am closing
this issue. Sorry.
> Unable to exclude current projects generated artifacts from the resulting
> JNLP file and zip.
> --------------------------------------------------------------------------------------------
>
> Key: MWEBSTART-110
> URL: http://jira.codehaus.org/browse/MWEBSTART-110
> Project: Maven 2.x Webstart Plugin
> Issue Type: Bug
> Affects Versions: 1.0-alpha-2
> Reporter: Chad Lyon
>
> There should be an option to exclude the currently generated artifacts from
> the JNLP file and from the zip file. This would help in aggregating
> dependencies into a component-desc type JNLP file that are all signed by the
> same certificate chain. For example, Sun signs alot of its JARs the same.
> One could create a JNLP containing multiple deps from Sun but this plugin
> tosses in the signed, generated JAR (even if empty) which has a different
> Cert chain and thus will cause webstart to reject it.
> This is related to MWEBSTART-14 in that the only time this is desirable is
> when trying to separately create component-desc JNLPs for use via the
> extension mechanism.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
