[
http://jira.codehaus.org/browse/MNG-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220870#action_220870
]
Benjamin Bentmann commented on MNG-4672:
----------------------------------------
This is yet another plugin bug (MWEBSTART-148) that shows only up under the
stricter runtime model of Maven 3.x (i.e. MNG-3297). Given this is now at least
the 3rd occasion of this particular issue, we might need to review MNG-3297 and
see whether that needs to be relaxed to only apply to plugins that somehow
indicate to target Maven 3.x.
> [regression] jnlp doesn't contains dependencies anymore when attaching
> sources to package phase
> -----------------------------------------------------------------------------------------------
>
> Key: MNG-4672
> URL: http://jira.codehaus.org/browse/MNG-4672
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.0-alpha-7, 3.0-beta-1
> Environment: Win XP
> Reporter: Julien HENRY
> Attachments: bug Maven 3 jnlp.zip
>
>
> running:
> mvn clean
> mvn package webstart:jnlp
> on the attached test project produce different result between Maven 2.2.1 and
> Maven 3-beta-1.
> With Maven 2 I have a jnlp and a zip file that contain all dependencies of
> the project (logback and slf4j in my sample project).
> With Maven 3 there is no dependency.
> Please note that the important point is that -sources generation is attached
> to the package phase (like with -DperformRelease=true). When I remove
> -sources generation it works with Maven 3.
--
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
