![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
1.0-beta-4 |
|
Assignee:
|
Unassigned |
|
Created:
|
21/Nov/13 9:18 AM
|
|
Description:
|
The order of the dependencies in the generated jnlp file must be constant through multiple sequential builds. This is needed when jnlp signing in the main jar is implemented (via JNLP-INF/APPLICATION.JNLP in the main jar).
Otherwise after a new deployment (without any changes in project dependencies) webstart may deny to start the application saying that the jnlp file signature is invalid. It seems that the jnlp file is cached locally by webstart and the cache invalidation logic is buggy. As a result webstart compares the old cached jnlp file against the main jar JNLP-INF/APPLICATION.JNLP which fails when dependencies order is different.
|
|
Project:
|
Mojo's Webstart Maven Plugin
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Marcus Linke
|
|
|
|
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
|
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
