Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] dependency:unpack fails in m2e with workspace resolution

m2e 1.0.0 is expected to work with Eclipse 3.6, I can't remember if m2e is finalized yet but at least an RC version is available at: http://download.eclipse.org/technology/m2e/milestones/1.0

On 8 June 2011 11:53, Derek Lewis <derek@xxxxxxxxxx> wrote:
Ok, that sounds great to me.  Thanks.  We're currently using Eclipse 3.6 /w m2e 0.12.2.  I plan to move us to Eclipse 3.7 /w m2e 1.0.0 not too long after it's out.


On 8 June 2011 05:56, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
m2e 1.0.0 is expected to skip this execution.

As I mentioned, m2e will create "plugin execution not covered" error
marker. The error marker has a quick fix to suppress it via pom.xml
configuration.

--
Regards,
Igor


On 11-06-08 12:23 AM, Derek Lewis wrote:
I suppose doing nothing would be better than doing the wrong thing.
What seemed to be happening in my build was that once m2e threw that
error, it stopped processing the project.  For example, the project has
a file in src/test/resources that I modified, but the modified file
wasn't being copied into target/test-classes, and I thought it might
have been because process-resources was failing due to the unpack.  If
it's marked as unsupported, as you've mentioned, will m2e skip that
execution, and carry on with the rest of the resources properly?  That
behaviour would be perfectly sufficient for what I'm trying to do.

On 7 June 2011 19:56, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<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
       m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>

       https://dev.eclipse.org/mailman/listinfo/m2e-dev

   _______________________________________________
   m2e-dev mailing list
   m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>

   https://dev.eclipse.org/mailman/listinfo/m2e-dev




_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev


_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev



Back to the top