[BUILD-72] Support for m2e / Eclipse Indigo ? Created: 03/Aug/11 Updated: 13/Apr/17 Resolved: 30/Apr/12 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | Poms |
| Affects Version/s: | None |
| Fix Version/s: | POMs 23 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
The latest version of Eclipse (Indigo) introduces m2e 1.0, which seems to cause some problems with plugins that are not "known" by m2e. This hits us with our setproperty plugin. Background info:
It would seem that adding the following to our parent pom might "solve" the issue. It doesn't seem like the most elegant thing, though ... <pluginManagement>
<plugins>
<!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>info.magnolia</groupId>
<artifactId>maven-setproperty-plugin</artifactId>
<versionRange>[1.1.1,)</versionRange>
<goals>
<goal>set-property</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute></execute>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
</plugins>
</pluginManagement>
The bug is being discussed at https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414 |
| Comments |
| Comment by Federico Grilli [ 17/Apr/12 ] |
|
Unfortunately there seems to be no alternative than adding the above snippet for all plugins complaining (I mean no alternative if you want/need to keep on using latest Eclipse). I've been using Indigo for one week now and have come across the following plugins not compliant with m2e connectors craziness so far For a moment I even thought about creating the missing connectors myself (possibly one connector to rule them all) but it looks like it is no fun http://grumpyapache.blogspot.com/2011/08/mess-that-is-m2e-connectors.html so I gave up the idea. In my experience, however annoying, the errors caused by the above-mentioned plugins' missing connectors did not affect my work - everything has worked fine so far (building modules, serving them from workspace, hot code deploy etc.) |
| Comment by Magnolia International [ 19/Apr/12 ] |
|
Ok, if there's only those 3 plugins, well… if it helps, why not; doesn't look like the problem is going to be fixed quickly at the core, so. I could add this to the next parent poms versions, in a profile, so the day it becomes outdated, it will hopefully be easier to remove/update/identify. (don't we already have an "eclipse" profile?) As a side note, since parent poms 20, we should be using Javadoc plugin 2.8 ( |
| Comment by Federico Grilli [ 23/Apr/12 ] |
|
Unfortunately Javadoc plugin 2.8 and 2.8.1 have the same problem as 2.7. |
| Comment by Magnolia International [ 30/Apr/12 ] |
|
Thanks Federico |