maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <>
Subject [jira] Commented: (MDEP-98) The source must not be a directory
Date Fri, 03 Aug 2007 01:59:13 GMT


Brian Fox commented on MDEP-98:

i can reproduce this with the IT now. This only happens on multi project builds where the
artifact is in the same reactor and the compile phase is used. Normally you will want to do
install for multimodule builds to work. The best I can do is detect I've been given a folder
and copy the contents of that folder instead of unpacking it. It's not clear what to do on
copy since you would normally expect the jar not the classes themselves.

> The source must not be a directory
> ----------------------------------
>                 Key: MDEP-98
>                 URL:
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: unpack-dependencies
>    Affects Versions: 2.0-alpha-4
>         Environment: Windows XP Professional SP2
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
>            Reporter: Pablo Muñiz
>            Assignee: Brian Fox
>             Fix For: 2.0-alpha-5
> Using maven-dependency-plugin in a multimodule project inside a module wich has a dependency
with another module in the same project the next error ocurrs : 
> org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
>         at org.codehaus.plexus.archiver.AbstractUnArchiver.validate(
>         at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(
>         at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(
>         at org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>         at org.apache.maven.DefaultMaven.doExecute(
>         at org.apache.maven.DefaultMaven.execute(
>         at org.apache.maven.cli.MavenCli.main(
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>         at java.lang.reflect.Method.invoke(
>         at org.codehaus.classworlds.Launcher.launchEnhanced(
>         at org.codehaus.classworlds.Launcher.launch(
>         at org.codehaus.classworlds.Launcher.mainWithExitCode(
>         at org.codehaus.classworlds.Launcher.main(
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] Error unpacking file: c:\D\desarrollo\proyectos\plataforma\platform-core\target\classes
to: c:\D\desarrollo\proyectos\plataforma\platform-bundle\platform-bundle-jar\target\classes
> org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
> Project structure is as follows:
> plataforma
>     - platform-core
>     - platform-bundle
>           - platform-bundle-jar
>           - platform-bundle-src
> and the error happens on executing any goal from parent pom. maven-dependency-plugin
seems to receive a reference to target/classes directory for platform-core dependency instead
of the URL to my local repository where platform-core is located.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message