m2e

问题 On Eclipse 4.3.2 my POM was using com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.5.1 with no problems. I tried to upgrade it to 3.8.2 (the latest), and I got the dreaded "Plugin execution not covered by lifecycle configuration" error. So of course I tried to do a "Quick Fix" of "Discover new m2e connectors". But the m2e Marketplace says "No marketplace items are available". What do I do? Other Information I have m2e-wtp - Maven Integration for WTP 1.0.1.20130911-1545 org

问题 I'm building a java project with Eclipse and the plugin m2e (it adds Maven support in Eclipse). There some XML Surefire reports ine the target directory. They generate annoying warnings because they have neither a DTD nor an XML Schema. How can you tell Eclipse to ignore **/target folders ? 回答1: See the following image: Open the preferences Window > Preferences 回答2: The whole target/ folder can be excluded from Eclipse's "management" by marking it as derived . Right-click on the target/

问题 While importing Spring Starter zipped project generated by Spring Initializr in Eclipse (STS　3.4) I got error Type Archive for required library: 'C:/Users/user/.m2/repository/org/springframework/spring-core/4.0.1.RELEASE/spring-core-4.0.1.RELEASE.jar' in project 'starter' cannot be read or is not a valid ZIP file Is it Eclipse problem or is there something special about spring-core-4.0.1.RELEASE.jar ? Its size is 979016B. Update: trying Answer https://stackoverflow.com/a/20093533/482717 to

问题 I have a web application (Eclipse's Dynamic Web App) which uses Maven (m2e-wtp) for the build and dependencies management. This web app's POM references a few other projects in my workspace, which happen to be eclipse plugins built with maven as well (built using Tycho), and also other third party libraries which come from Maven's repository. Everything works fine when I run maven from the CLI. All dependencies are included in the WEB-INF/lib directory just as expected. The problem is when I

问题 I am having some problems getting Eclipse to honour a test-scoped Maven dependency - it is showing up on the build path and messing with eclipse's compilation / javadoc resolution. An example with Java EE libs I have been using the javaee-api-6.0 library to compile my Java EE application against. However, for unit testing purposes, I wanted to have access to more than just the api - I needed an implementation. So I included the embedded glassfish libs with a test scope like so: <repositories>

问题 After recently converting to Maven from Ant, run configurations that launched immediately pre-Maven take an excessive amount of time and consume an abnormal amount of resources while Eclipse prepares to launch the projects. Eclipse shows this status message: Verifying launch attributes... At 57% completion, Eclipse hangs for several minutes before finally launching the run configuration. Once launched, the project runs fine and without a problem. I found this blog article that suggested to

问题 All our projects are built using maven. we have centralized some of our main configuration within a super pom. In order to always have an update version of this super pom (without having to modify the version), we have used the following syntax : <parent> <groupId>my.organization</groupId> <artifactId>superPom</artifactId> <version>RELEASE</version> </parent> The problem is that Maven Eclipse plugin (m2e) doesn't understand this syntax (the RELEASE constant is not resolved). So, our Eclipse

问题 Here is the layout of my project: src/ test/ resources/ ares/ file1.xml file2.xml Here is the layout of the Jenkins workspace: my-module/ target/ test-classes/ ares/ file1.xml file2.xml Under eclipse the tests run without any error. On Jenkins, the tests just fail. Jenkins is unable to locate the resources. Below are some output from the test execution: Eclipse MyClass.class.getResourceAsStream(/ares/file1.xml) => java.io.BufferedInputStream@4f4b2f1a MyClass.class.getResourceAsStream(ares

问题 I'm almost new with Osgi. I'm using Eclipse 3.6 Helios for building my first Felix Bundle but find out that M2E don't understand bundle packaging... Project build error: Unknown packaging: bundle Project build error: Unresolveable build extension: Plugin org.apache.felix:maven-bundle-plugin:2.0.0 or one of its dependencies could not be resolved: Failed to collect dependencies for org.apache.felix:maven-bundle-plugin:jar:2.0.0 () As I done google searches, it was an error in Maven 2 but fixed

问题 Does anyone know any simple yet effective way to build all Maven projects in current workspace, for example, maven clean install for each such project. Is it for example possible to select multiple projects and use something similar to ${project_loc} or get a popup with possible projects to use for the run configuration? Or any other way? I'm using Eclipse Juno. 回答1: Can you give them all a parent pom.xml and then mvn compile the parent pom.xml? Look for project inheritance here. If you can