[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] Eclipse 3.7 with m2 Feedback
|
To be clear, adding <execute/> mapping to pom.xml is almost certainly
not a good idea, especially for maven plugins that generate code in
eclipse workspace. Wiki [1] provides some background information about
bad side-effects of executing maven plugins inside eclipse workspace.
I realize that lack of out-of-the-box support for many popular maven
plugins appears to be a significant regression compared to 0.12, but I
am hopeful that we, as a community, will be able to quickly populate m2e
extensions discovery catalog and effectively solve this problem. For
everyone interested to help [2] provides some pointers where to start
and m2e developers will be happy to help on m2e-dev mailing list.
[1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered
[2] http://wiki.eclipse.org/M2E_Extension_Development
--
Regards,
Igor
On 11-06-25 10:24 AM, Alexander Vaysberg wrote:
Hi,
I've tried Eclipse Plugin 3.7 and M2E (M2E Eclipse 1.0.0) and find
that for normal use it is not acceptable:
Problem number 1: Life cycle
M2E plugin in Eclipse 3.6 has all the extensions of life cycle without a
problem
taken.Now we should make all POM M2e-dependent with
one:
<pluginManagement>
<plugins>
<plugin>
<groupId> org.eclipse.m2e </ groupId>
<artifactId> lifecycle mapping </ artifactId>
<version> 1.0.0 </ version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId> some-group-id </ id>
<artifactId> some-artifact-id </ artifactId>
<versionRange> [1.0.0,) </ version range>
<goals>
<goal> some-goal </ goal>
</ Goals>
</ PluginExecutionFilter>
<action>
<Execute />
</ Action>
</ PluginExecution>
</ PluginExecutions>
</ LifecycleMappingMetadata>
</ Configuration>
</ Plugin>
</ Plugins>
</ Plugin management>
Why? And that's not acceptable.I have seen many over
read and can only say one: -the people are unhappy!!In other
Java tools works it better (NetBean, IntelliJDEA).You can ignore it, but
no Java tool is used without Maven.This is solved
be.
Problem number 2: Maven and Spring IDE.
I installed Spring IDE 2.7 with the Maven support in Eclipse 3.7 and M2E
was gone :(.
So wait and stay on Eclipse 3.6,or other Java tool
use.
Alexander Vaysberg
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
