As I explain in [1], m2e and maven-eclipse-plugin implement two distinct and incompatible maven/eclipse integration approaches. Don't try to mix them for the same project.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=374332#c15 -- Regards, Igor On 2013-05-31 11:52 PM, Artur Drummond wrote:
Hey guys! I've already found one workaround for this problem but I'd like to understand more about the plugin and maven tasks and try to implement a definitive solution. The workaround can be found here: http://stackoverflow.com/questions/10564684/how-to-fix-error-updating-maven-project-unsupported-iclasspathentry-kind-4 I have a maven project in Eclipse Juno SR2 and every time that I run the task "eclipse:eclipse"on this project, maven re-generate .classpath. No problem, right? After all, this was the purpose of this task... however the problem is HOW the .classpath file is generated. Usually, this task include many "var" referencing the jars from my "~/.m2" repository. Here is an example of one line containing the use of var: <classpathentrykind="var"path="M2_REPO/javax/javaee-web-api/6.0/javaee-web-api-6.0.jar"/> The problem is when I try to use this option after: Inline image 1 I got the following problem: Inline image 2 This is very common problem and a little but annoying (usually other programmers commit .classpath after generating with eclipse:eclipse) What do you guys can suggest me? Thanks, Artur Drummond _______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users
