Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
None
Description
The protocol module build sometimes fails with a:
[INFO] --- maven-dependency-plugin:2.1:unpack-dependencies (Extract xsd files) @ bitrepository-protocol ---
[INFO] Unpacking /Users/mss/projects/bitmagasin/bitrepository-message-xml/target/classes to
/Users/mss/projects/bitmagasin/bitrepository-protocol/target/message-xml
with includes examples/messages/*.xml,xsd/*.xsd and excludes:null
org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
at org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:174)
at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:107)
at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260)
at org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:90)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
....
error. This is properly because the dependency plugin tries to look for the files to extract in the target folder. The problem seems to vary based on target and Maven version (Maven 3 builds seem more fragile), this indicates that the exact classpath sequence is affecting the success and failure of this build functionality.
A number of dependency plugin bugs are registered which relates to this problem, see MDEP-194 ArchiverException when using maven dependency plugin in multi-module projects