Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Maven plugin v1.4.4 'check' mojo crashes on multi-modules project

See original GitHub issue

Consider a Maven multi-modules project : a parent with jar & war modules, the war using the jar (like hierarchical-cross-deps.zip.txt, to rename in zip, won’t be uploaded).

On command :
mvn install org.owasp:dependency-check-maven:1.4.4:check -e

The plugin crashes with:

[ERROR] Failed to execute goal org.owasp:dependency-check-maven:1.4.4:check (default-cli) on project XXX: One or more exceptions occurred during dependency-check analysis: One or more exceptions occurred during dependency-check analysis
[ERROR] null
[ERROR] null
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.owasp:dependency-check-maven:1.4.4:check (default-cli) on project XXX: One or more exceptions occurred during dependency-check analysis
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
  [...]
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: One or more exceptions occurred during dependency-check analysis
	at org.owasp.dependencycheck.maven.CheckMojo.runCheck(CheckMojo.java:119)
	at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.execute(BaseDependencyCheckMojo.java:465)
  [...]
	... 20 more
Caused by: org.owasp.dependencycheck.exception.ExceptionCollection: One or more exceptions occurred during dependency-check analysis
	null
	null
	at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:543)
	at org.owasp.dependencycheck.maven.MavenEngine.analyzeDependencies(MavenEngine.java:95)
	at org.owasp.dependencycheck.maven.CheckMojo.runCheck(CheckMojo.java:96)
	... 23 more

The problem occurs only on parent, with version 1.4.4 (works fine with previous versions).

Issue Analytics

State:
Created 7 years ago
Comments:14 (13 by maintainers)

Top GitHub Comments

3reactions

jeremylongcommented, Dec 3, 2016

I just released the Maven plugin version 1.4.4.1 to resolve this issue.

0reactions

lock[bot]commented, Sep 28, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Top Results From Across the Web

Sonar-maven-plugin not working with multi-module maven ...

Where app , dbsync , mock-rest are child maven modules of the main project pom.xml config. The jococo coverage reports are generated ...

Basic maven plugin project not working, Mojo ... - Stack Overflow

For my plugin projects, i could workaround by adding an explicit execution of the maven-plugin-plugin: <build> <plugins> <plugin> ...

Maven Assembly Plugin fails with Clover - OpenClover

project is using the maven-assembly-plugin; project is a multi-module Maven project ... MojoExecutionException: Failed to create assembly: Error creating ...

Multi-Module Maven Application with Java Modules - Baeldung

Learn to create a multi-module Maven application using the Java ... make sure to check the latest version of the plugin on Maven...

SonarQube with JaCoCo in multi-module Maven project

How to set up a SonarQube code analysis using the Sonar Maven Plugin including code coverage with the JaCoCo Maven plugin.