m2eclipse | 易学教程

Plugin execution not covered by lifecycle configuration (JBossas 7 EAR archetype)

阅读更多关于 Plugin execution not covered by lifecycle configuration (JBossas 7 EAR archetype)

I am using Eclipse 3.7 Indigo with Maven M2E Plugin 1.0.100. Using the JBoss 7.x JavaEE 6 EAR archetype, the pom for EAR is giving me this error: Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-ear-plugin:2.6:generate-application-xml (execution: default-generate-application-xml, phase: generate-resources) <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-ear-plugin</artifactId> <version>2.6</version> <configuration>  <version>6</version> <!-- Use Java EE ear libraries as needed. Java EE ear

Missing Maven dependencies in Eclipse project

阅读更多关于 Missing Maven dependencies in Eclipse project

问题 We have a project set up with maven for resolving dependancies. It usually works fine, but now I am trying to compile and run it on a new PC and I have problem with missing dependencies in Eclipse. What is funny is that if I run \"mvn package\" in console or in eclipse, it works fine and even produces war containing all necessary jars. Only Eclipse complains with \"The project was not built since its build path is incomplete. Cannot find the class file for org.slf4j.Logger...\". If I compare

Failed to resolve version for org.apache.maven.archetypes

阅读更多关于 Failed to resolve version for org.apache.maven.archetypes

问题 I have configured maven3.0.3 in my local machine. Have installed m2e eclipse plugin. But when i try to create a new maven project using maven-archetype-webapp, i get the following exception. Could not resolve archetype org.apache.maven.archetypes:maven-archetype-webapp:RELEASE from any of the configured repositories. Could not resolve artifact org.apache.maven.archetypes:maven-archetype- webapp:pom:RELEASE Failed to resolve version for org.apache.maven.archetypes:maven-archetype- webapp:pom

“Faceted Project Problem (Java Version Mismatch)” error message

阅读更多关于 “Faceted Project Problem (Java Version Mismatch)” error message

问题 Eclipse\'s \"problems\" tab is displaying this error: Description: Java compiler level does not match the version of the installed Java project facet. Resource: groupping Path: [blank] Location: Unknown Type: Faceted Project Problem (Java Version Mismatch) My pom.xml has this setting: <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.6</source> <target>1.6</target> </configuration> </plugin> </plugins> Where

Maven “build path specifies execution environment J2SE-1.5”, even though I changed it to 1.7

阅读更多关于 Maven “build path specifies execution environment J2SE-1.5”, even though I changed it to 1.7

问题 In Eclipse Juno, I installed the latest m2e plugin (1.2.20120903-1050). In preferences, I have added jdk1.7.0_11 in Java -> Installed JREs -> Add, and then specified the location ( C:\\Program Files\\Java\\jdk1.7.0_11 ). When I create a new Maven project and run it, I get a warning: Build path specifies execution environment J2SE-1.5. There are no JREs installed in the workspace that are strictly compatible with this environment. I am not sure how to resolve this. I believe it is a Maven

What causes imported Maven project in Eclipse to use Java 1.5 instead of Java 1.6 by default and how can I ensure it doesn't?

阅读更多关于 What causes imported Maven project in Eclipse to use Java 1.5 instead of Java 1.6 by default and how can I ensure it doesn't?

问题 I imported a Maven project and it used Java 1.5 even though I have 1.6 configured as my Eclipse default Preferences->Java->Installed JREs . When I changed the Maven project to use the 1.6 JRE it still had the build errors left over from when the project was using Java 1.5 (I described these build errors earlier in: I have build errors with m2eclipse but not with maven2 on the command line - is my m2eclipse misconfigured?) I\'m going to delete the project and try again but I want to make sure

How do I set the eclipse.ini -vm option?

阅读更多关于 How do I set the eclipse.ini -vm option?

问题 I installed the Maven plugin for Eclipse, and then I got an error like below: please make sure the -vm option in eclipse.ini is pointing to a JDK How do I use the -vm option to point to my JDK in eclipse.ini? 回答1: My solution is: -vm D:/work/Java/jdk1.6.0_13/bin/javaw.exe -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256M -framework plugins\org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar -vmargs -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx512m 回答2: eclipse.ini file must have -vm on

M2E and having maven generated source folders as eclipse source folders

阅读更多关于 M2E and having maven generated source folders as eclipse source folders

问题 I have a maven project in eclipse and have maven goals that run annotation processors to generate code. The output folder for this code is target/generated-sources/apt. In order for eclipse to see this generated code I need to add target/generated-sources/apt as a source folder to the eclipse project. However, this causes there to be an error of type \"Maven Configuration Problem\" saying Project configuration is not up-to-date with pom.xml. Run project configuration update I think I

Plugin execution not covered by lifecycle configuration (JBossas 7 EAR archetype)

阅读更多关于 Plugin execution not covered by lifecycle configuration (JBossas 7 EAR archetype)

问题 I am using Eclipse 3.7 Indigo with Maven M2E Plugin 1.0.100. Using the JBoss 7.x JavaEE 6 EAR archetype, the pom for EAR is giving me this error: Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-ear-plugin:2.6:generate-application-xml (execution: default-generate-application-xml, phase: generate-resources) <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-ear-plugin</artifactId> <version>2.6</version> <configuration> <!-- Tell Maven

Maven: best way of linking custom external JAR to my project?

阅读更多关于 Maven: best way of linking custom external JAR to my project?

It's my first couple of days learning Maven and I'm still struggling with the basics. I have an external .jar file (not available in the public repos) that I need to reference in my project and I'm trying to figure out what my best option is. It's a small scale project without a central repository for libraries, so it has to be either a local repository (somehow added to source control, don't know if it's supposed to work that way?) or the .jar needs to be stored on disk outside of any formal repository. 1) What's my best option for adding the .jar file to my project's references with maven