[BUILD-199] Updated maven-dependency-plugin to 2.10 (dependency:analyze doesn't work on multi-module-projects with 2.9) Created: 16/Mar/15  Updated: 08/May/15  Resolved: 16/Mar/15

Status: Closed
Project: Build
Component/s: Build Tools
Affects Version/s: None
Fix Version/s: POMs 31

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Doing an mvn dependency:analyze on a multi-module-project doesn't work with version 2.9 of the maven plugin.

See: https://jira.codehaus.org/browse/MDEP-466

A workaround is to downgrade the plugin to 2.8:

mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:analyze
Error looks like this:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.9:analyze (default-cli) on project magnolia-theme-pop: Cannot analyze dependencies: /Users/johndoe/code/modules/standard-templating-kit/magnolia-module-standard-templating-kit/target/classes (Is a directory) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :magnolia-theme-pop
Added workaround to the following modules
  • site (master)
  • stk (master)
  • templating-essentials (master)
  • categorization (master)


 Comments   
Comment by Magnolia International [ 16/Mar/15 ]

Let's try with 2.10; if that works, we can easily do this with poms 31

Comment by Magnolia International [ 16/Mar/15 ]

Just gave this a shot with the Site module, seems to work

Generated at Sun Feb 11 23:39:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.