| M2E and IAM should get their act together and agree on a common classpathentry for both plugins [message #507281] |
Tue, 12 January 2010 18:01 |
 Lars Sonchocky-Helldorf
Messages: 13
Registered: July 2009 |
Junior Member |
|
|
- IAM and M2E should use the same classpathentry, now for IAM it is <classpathentry kind="con" path="org.eclipse.iam.jdt.core.mavenClasspathContainer"> while M2E uses <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_
CONTAINER"/>
This is very annoying since in our company some developers use IAM others use M2E. So now the .classpath files of the projects here bear eater the IAM or the M2E classpathentry, depending on who started the project. Having installed both plug ins is also not an solution since some projects even have both classpathentries in their .classpath. In this case both plugins start to fight each other (I always remove the M2E classpathentry then but others who don't know Eclipse that well have their hard time).
So please get your act together (IAM and M2E) and to come to an agreement on a common classpathentry for both of your plug ins!
@M2E & IAM: Please bury the hatchet and start to cooperate!
|
|
|
Powered by
FUDForum. Page generated in 0.02887 seconds
] 
Search
Help
Register
Login
Home
