[MNG-4672] [regression] jnlp doesn't contains dependencies anymore when attaching sources to package phase

[jira-importer]

Julien HENRY opened MNG-4672 and commented

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.

---

Affects: 3.0-alpha-7, 3.0-beta-1

Attachments:

• bug Maven 3 jnlp.zip (1.88 kB)

Issue Links:

• MNG-3297 maven should not give dependencies to plugins that don't @requireDependencyResolution

[jira-importer]

Benjamin Bentmann commented

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.

[jira-importer]

Benjamin Bentmann commented

FWIW, mvn package webstart:jnlp*-inline* works.

[jira-importer]

Julien HENRY commented

Thanks for the workaround, I confirm it works on my "real" project too.

[jira-importer]

Tony Chemit commented

Can this issue be closed now ?

[jira-importer]

Jason van Zyl commented

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014

[jira-importer]

Jason van Zyl commented

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.