<mailto:
igor@xxxxxxxxxxxxxx>> wrote:
Can you describe desired behaviour in some details? Do you expect m2e to
honour maven-jar-plugin configuration of ep-search project, for example?
Should dependency:unpack happen incrementally. whenever anything under
ep-search/target/classes changes? What if ep-search has some
dependency:unpack magic of it's own, should m2e follow that too?
We could not find a good general answer to these questions, so 1.0.0
will mark dependency:unpack as unsupported (see still unfinished [1])
but will ignore it otherwise.
m2e can be configured or extended to do something smarter (it is not too
late in other words, this kind of changes can happen without touching
m2e itself), but at this point we don't know what this smarter logic
should be or at least how to implement it.
[1]
http://wiki.eclipse.org/M2E_plugin_execution_not_covered
--
Regards,
Igor
On 11-06-07 8:39 PM, Derek Lewis wrote:
I ran across another incarnation of this rather old bug today:
http://jira.codehaus.org/browse/MDEP-187
With this in our pom:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>unpack</id>
<phase>process-resources</phase>
<goals>
<goal>unpack</goal>
</goals>
</execution>
</executions>
<configuration>
<artifactItems>
<artifactItem>
<groupId>com.elasticpath</groupId>
<artifactId>ep-search</artifactId>
<overWrite>true</overWrite>
<outputDirectory>target/</outputDirectory>
<includes>...</includes>
</artifactItem>
</artifactItems>
</configuration>
</plugin>
and com.elasticpath:ep-search open in Eclipse, and workspace
resolution
enabled, I get this error:
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal
org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack
(unpack) on project ep-search-itest: Error unpacking file:
/home/dlewis/projects/maven-migration-testing/ep/ep-search/target/classes
to:
/home/dlewis/projects/maven-migration-testing/ep/ep-search-itest/target
Is there any possibility of getting this fixed before the final
1.0.0
goes out in Eclipse 3.7, or is it too late for that?
_______________________________________________
m2e-dev mailing list
