Hello,
I'm running into a build error when I force clean on my
eclipse project.  During the process-test-resources phase, I need to
copy a dependency jar into a folder for my test cases to find and link
with.  This configuration works fine using maven at the command line,
but using m2eclipse v 0.96 and 0.97 I am getting this error:

11/14/08
11:19:42 AM EST: Build errors for content;
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
in the plugin manager executing goal
'org.apache.maven.plugins:maven-dependency-
plugin:2.0:copy': Mojo execution failed.

When I enable debug output, I do not see any new information regarding the 
error.
I am using eclipse 3.4 and I have set up to use the external install of maven 
version 2.09

Here is how I configured the dependency plugin:

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
                <version>2.0</version>
                <executions>
                    <execution>
                        <id>copy</id>
                        <phase>process-test-resources</phase>
                        <goals>
                            <goal>copy</goal>
                        </goals>
                        <configuration>
                            <artifactItems>
                                <artifactItem>
                                    <groupId>com.mygroup</groupId>
                                    <artifactId>my-artifact</artifactId>
                                    <version>${my-artifact.version}</version>
                                    <type>jar</type>
                                    
<outputDirectory>${basedir}/target/test-classes/dependencies</outputDirectory>
                                    <overWrite>true</overWrite>
                                </artifactItem>
                            </artifactItems>
                        </configuration>
                    </execution>
                </executions>
            </plugin>


Is there a workaround for this or is this a bug?
Thanks


      

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to