[
http://jira.codehaus.org/browse/MWEBSTART-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256418#action_256418
]
Farrukh Najmi commented on MWEBSTART-162:
-----------------------------------------
The workaround so far is to add as explicit <jarResource/> elements for each
dependency that you want to force a specific version for in the resulting jnlp.
This is very painful and brittle but does work around the issue.
> jnlp-download-servlet does not respect dependencyManagement when resolving
> transitive dependencies for JarResource in JnlpFile
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: MWEBSTART-162
> URL: http://jira.codehaus.org/browse/MWEBSTART-162
> Project: Maven 2.x Webstart Plugin
> Issue Type: Bug
> Components: jnlp-download-servlet
> Affects Versions: 1.0-beta-1
> Reporter: Farrukh Najmi
>
> I have very carefully done dependencyManagement for spring jars in my that
> are dependencies for my JNLP app.
> When using the webstart-maven-plugin with the jnlp-download-servlet mojo the
> versions specified via dependencyManagement are not respected causing fatal
> errors due to version mismatches between dependencies.
> The correct behavior would be for the jnlp-download-servlet mojo to respect
> dependencyManagement specified version when retrieving transitive
> dependencies.
--
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
