m2e

After starting Eclipse, Mven seems to set the compiler settings to 1.5 and forget all the other global code style settings to ensure a higher code quality. Is there some way to disable this feature? Or can I specify all compiler and code style checks in my POM? It is very annoying because Ecplise can't run the app because of not allowed override annotations for interfaces. The tick in Java compiler -> Enable project specific settings is always set after a restart. You can set the compiler source and target (byte-code) versions in your pom. See http://maven.apache.org/plugins/maven-compiler

I've updated to lastest version of ADT Plugin and I faced this issue , solved updating also m2e-android eclipse plugin. Now, I'm able to compile my project through console, but not with eclipse. This is the exception thrown by pom.xml file in eclipse: dependency=[com.actionbarsherlock:library:apklib:4.1.0:compile] not found in workspace In previous versions of ADT/m2e-android, I was able to build both console and eclipse without problems. Does anyone know how to solve this? Maybe my pom.xml is wrong? Thanks for your time. Currently using: Eclipse classic 3.7.2 (with Juno the problem persists)

We have a rather complicated multi-module Maven project. There are Flex modules, GWT modules, Java modules, and a number of WAR modules. In order to simply the process of importing these projects into Eclipse, historically we have included all the relevant Eclipse project files in the source tree. However, this has been a source of problems in the past because sometimes those files are modified accidently and checked in...thus causing problems for other developers. With the advent of M2E and its new support for configurators to help set up Eclipse projects upon import, we are rethinking this

Ever since I've installed the new m2e plugin for maven, my Groovy project no longer builds. I'm using the groovy-compiler-plugin as described here . I get the old "plugin execution not covered..." error for the maven-compiler-plugin. I've tried both execute and ignore for the goals "testCompile" and "compile" as described in the error. I can't use GMaven due to some arcane compiler issues. I also am locked to Maven 2.2.1 due to my company's build process. The old m2eclipse plugin is gone, and the documentation for m2e is atrocious. I am at my wits end with this. Nowhere else do I see this

一直以来困扰我的一个问题终于解决了，就是用m2eclipse导入 mvn archetype:create 命令建立的项目总是报错的问题。 一般来说建立Maven web最快捷的方式就是用 mvn archetype:create -DarchetypeArtifactId=maven-archetype-webapp 这个命令了，但是之后导入eclipse却是一件麻烦事， 创建完了以后，我们一般用执行mvn eclipse:eclipse来转换为eclipse项目，然后mvn eclipse:clean一项，然后 就可以通过m2eclipse导入到IDE中区了，但是你一运行Maven build命令一般会包这个错 An internal error occurred during: "Importing Maven projects". Unsupported IClasspathEntry kind=4 这个就是m2eclipse的bug，据说从m2e1.0版本的插件时就有了，我现在安装的是m2e1.4版本的插件。还是没解决这个问题 这个是从 stack 上获得的解决方法 标准的解决办法，非常完美(为了偷懒，就直接copy过来了，呵呵……) 这个大问题算 解决了，还有 一些小问题， http://blog.csdn.net/yuguiyang1990/article

I’m using Eclipse Kepler on Mac 10.9.5. I have imported a number of Maven projects using the m2e Eclipse plugin. All these projects are children of a parent pom. When I look at the “Overview” in the individual child pom.xml files, I see stuff like this: Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:properties-maven-plugin:1.0-alpha-2:write-project-properties (execution: default, phase: process-resources) I would like Eclipse to execute these lifecycle phases at the appropriate times, but I’m not sure how to do that. When I select Eclipse’s suggestion … Permanently

I am using Eclipse 3.7.2 + Android + Maven + m2e and I have a problem with Android libraries included via Maven as apklibs. I built a test scenario with two projects, mvntest1 (the main project) and mvntest2 (my library project). The pom.xml 's are included after this text. So far so good. I can build mvntest2 via console $ mvn install without any errors. Thus, I have an apklib in my local maven repository ( ~/.m2/repository/mvntest2/mvntest2/0.0.1-SNAPSHOT/mvntest2-0.0.1-SNAPSHOT.apklib ). But: The including does not work. Eclipse does not include the classes, etc. of mvntest2 in mvntest1 . I