[#MDEP-187] dependency:copy fails when invoked from m2e with workspace resolution enabled - jira.codehaus.org

Details

Type: Bug
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: 2.1
Fix Version/s: None
Component/s: None
Labels:
None

Number of attachments :
2

Description

m2e resolves workspace artifacts to their output folders but dependency:copy expects all artifacts to be files. I will provide trivial patch shortly.

More Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

MDEP-187.diff

12/Nov/08 4:27 PM

0.9 kB

Igor Fedorenko
MDEP-187b.diff

13/Nov/08 12:15 PM

6 kB

Igor Fedorenko

Issue Links

This issue duplicates:
MDEP-98	The source must not be a directory

This issue is duplicated by:
MDEP-194	ArchiverException when using maven dependency plugin in multi-module projects
MDEP-98	The source must not be a directory
MDEP-195	dependency resolution fails when modules have inter-dependencies

This issue relates to:
MASSEMBLY-411	Error on copy dependencies using Assembler Plugin (m2e Eclipse Plugin Workspace Resolution)

This issue is depended upon by:
MNGECLIPSE-1027	[mng] Workspace dependency resolution doesn't work with maven-dependency-plugin

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Igor Fedorenko added a comment - 13/Nov/08 12:15 PM

updated path that fixes same exception in unpack mojo and also includes two unit tests.

Show

Igor Fedorenko added a comment - 13/Nov/08 12:15 PM updated path that fixes same exception in unpack mojo and also includes two unit tests.

Hide

Permalink

Marcelo Alcantara added a comment - 08/Apr/09 1:53 PM

I was having the same problem as mentioned on the MNGECLIPSE-1027 and saw the recomendation to update the maven-dependency-plugin to version 2.1.

I updated the plugin but still have the same problem.

Any ideas?

Show

Marcelo Alcantara added a comment - 08/Apr/09 1:53 PM I was having the same problem as mentioned on the MNGECLIPSE-1027 and saw the recomendation to update the maven-dependency-plugin to version 2.1. I updated the plugin but still have the same problem. Any ideas?

Hide

Permalink

Felipe Desiderati added a comment - 30/Apr/09 10:59 AM

I have the same problem too, and the only solution I´ve found was to simply disable workspace resolution. I know that is terrible and with this approach I have to install locally all the time the other dependent projects
Meanwhile, waiting for the fix.

Show

Felipe Desiderati added a comment - 30/Apr/09 10:59 AM I have the same problem too, and the only solution I´ve found was to simply disable workspace resolution. I know that is terrible and with this approach I have to install locally all the time the other dependent projects

Meanwhile, waiting for the fix.

Hide

Permalink

Julien Wajsberg added a comment - 05/Jun/09 8:18 AM

Is it possible to have this patch applied if it works ?

Thanks.

Show

Julien Wajsberg added a comment - 05/Jun/09 8:18 AM Is it possible to have this patch applied if it works ? Thanks.

Hide

Permalink

derek added a comment - 11/Aug/09 3:31 AM

Is there any other workarounds for this one?
Thanks,
Derek

Show

derek added a comment - 11/Aug/09 3:31 AM Is there any other workarounds for this one? Thanks, Derek

Hide

Permalink

Clint Shank added a comment - 16/Nov/09 10:20 AM

My current workaround for this issue is to use the antrun plug-in. For example,

<plugin>
    <artifactId>maven-antrun-plugin</artifactId>
    <executions>
      <execution>
        <!-- copy just built artifact to some lib dir -->
        <id>copy-to-lib</id>
        <goals>
          <goal>run</goal>
        </goals>
        <phase>package</phase>
        <configuration>
          <tasks>
            <copy
                file="${project.build.directory}/${project.build.finalName}.${project.packaging}"
                tofile="${some.lib.dir}/${project.artifactId}.${project.packaging}" />
          </tasks>
        </configuration>
      </execution>
    </executions>
  </plugin>

This allows "Resolve dependencies from Workspace projects" to work.

Show

Clint Shank added a comment - 16/Nov/09 10:20 AM My current workaround for this issue is to use the antrun plug-in. For example,

<plugin>
    <artifactId>maven-antrun-plugin</artifactId>
    <executions>
      <execution>
        <!-- copy just built artifact to some lib dir -->
        <id>copy-to-lib</id>
        <goals>
          <goal>run</goal>
        </goals>
        <phase>package</phase>
        <configuration>
          <tasks>
            <copy
                file="${project.build.directory}/${project.build.finalName}.${project.packaging}"
                tofile="${some.lib.dir}/${project.artifactId}.${project.packaging}" />
          </tasks>
        </configuration>
      </execution>
    </executions>
  </plugin>

This allows "Resolve dependencies from Workspace projects" to work.

Hide

Permalink

Nathan Wells added a comment - 18/Mar/10 9:15 PM

It seems that there are many duplicates of this issue, or that the issue manifests itself in many different ways.

Show

Nathan Wells added a comment - 18/Mar/10 9:15 PM It seems that there are many duplicates of this issue, or that the issue manifests itself in many different ways.

Hide

Permalink

Walt added a comment - 06/Sep/11 5:59 PM - edited

I'm hitting this problem from the command line.

<plugin>
                <artifactId>maven-dependency-plugin</artifactId>
                <executions>
                    <execution>
                        <id>obtain instrumentation candidates</id>
                        <phase>generate-sources</phase>
                        <goals>
                            <goal>unpack</goal>
                        </goals>
                        <configuration>
                            <artifactItems>
                                <artifactItem>
                                    <groupId>${project.groupId}</groupId>
                                    <artifactId>my-control-plugins</artifactId>
                                </artifactItem>
                                <artifactItem>
                                    <groupId>${project.groupId}</groupId>
                                    <artifactId>my-control-plugins</artifactId>
                                    <classifier>sources</classifier>
                                    <includes>**/GeneratedPlugin.java</includes>
                                    <outputDirectory>${project.build.sourceDirectory}</outputDirectory>
                                </artifactItem>
                            </artifactItems>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

gives me

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.3:unpack (obtain instrumentation candidates) on project my-control-plugins-cobertura: Error unpacking file: /home/me/devel/my/execution/exec-plugins/my-control-plugins/target/classes to: /home/me/devel/execution/exec-plugins/my-control-plugins-cobertura/target/dependency
[ERROR] org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.3:unpack (obtain instrumentation candidates) on project oo-control-plugins-cobertura: Error unpacking file: /home/me/devel/execution/exec-plugins/my-control-plugins/target/classes to: /home/me/devel/execution/exec-plugins/my-control-plugins-cobertura/target/dependency
org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error unpacking file: /home/me/devel/execution/exec-plugins/my-control-plugins/target/classes to: /home/me/devel/execution/exec-plugins/my-control-plugins-cobertura/target/dependency
org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
	at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:267)
	at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:116)
	at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:94)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
	... 19 more
Caused by: org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
	at org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:185)
	at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:118)
	at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:258)
	... 23 more

From the looks of it, this has been an issue now for 4 years and it's still not fixed?????

Show

Walt added a comment - 06/Sep/11 5:59 PM - edited I'm hitting this problem from the command line.

<plugin>
                <artifactId>maven-dependency-plugin</artifactId>
                <executions>
                    <execution>
                        <id>obtain instrumentation candidates</id>
                        <phase>generate-sources</phase>
                        <goals>
                            <goal>unpack</goal>
                        </goals>
                        <configuration>
                            <artifactItems>
                                <artifactItem>
                                    <groupId>${project.groupId}</groupId>
                                    <artifactId>my-control-plugins</artifactId>
                                </artifactItem>
                                <artifactItem>
                                    <groupId>${project.groupId}</groupId>
                                    <artifactId>my-control-plugins</artifactId>
                                    <classifier>sources</classifier>
                                    <includes>**/GeneratedPlugin.java</includes>
                                    <outputDirectory>${project.build.sourceDirectory}</outputDirectory>
                                </artifactItem>
                            </artifactItems>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

gives me

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.3:unpack (obtain instrumentation candidates) on project my-control-plugins-cobertura: Error unpacking file: /home/me/devel/my/execution/exec-plugins/my-control-plugins/target/classes to: /home/me/devel/execution/exec-plugins/my-control-plugins-cobertura/target/dependency
[ERROR] org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.3:unpack (obtain instrumentation candidates) on project oo-control-plugins-cobertura: Error unpacking file: /home/me/devel/execution/exec-plugins/my-control-plugins/target/classes to: /home/me/devel/execution/exec-plugins/my-control-plugins-cobertura/target/dependency
org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error unpacking file: /home/me/devel/execution/exec-plugins/my-control-plugins/target/classes to: /home/me/devel/execution/exec-plugins/my-control-plugins-cobertura/target/dependency
org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
	at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:267)
	at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:116)
	at org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:94)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
	... 19 more
Caused by: org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
	at org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:185)
	at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:118)
	at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:258)
	... 23 more

From the looks of it, this has been an issue now for 4 years and it's still not fixed?????

People

Assignee:

Brian Fox

Reporter:

Igor Fedorenko

Vote (40)

Watch (31)

Dates

Created:

12/Nov/08 4:26 PM

Updated:

06/Sep/11 6:02 PM

Maven 2.x Dependency Plugin

dependency:copy fails when invoked from m2e with workspace resolution enabled

Details

Description

Attachments

Issue Links

Activity

People

Dates