m2eclipse

Version 1.8 of project facet java does not exist

 ̄綄美尐妖づ 提交于 2019-11-27 00:33:42
问题 I'm trying to build a Dynamic Web Application in eclipse using Java 8 (and Wildfly appServer if that matters) but I'm unable to make Eclipse Luna M5 use Java 8 (I do have Java 8 BETA support installed and it works on JavaSE projects). In my POM I set the level to Java 8: <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>3.1</version> <configuration> <source>1.8</source> <target>1.8</target> </configuration> </plugin> But after I do maven -> update project I get the following

How to exclude a folder that is producing warnings/errors in an Eclipse project?

流过昼夜 提交于 2019-11-27 00:33:06
问题 Okay. I'm sick of this problem. This has to have an easy fix, I'm sure of it!! I hope SO can help me to get rid of this once and for all! Question How do we get Eclipse to stop trying to process/compile all files under a particular project directory? The goal is for no errors/warnings to exist in the problems view if they relate to something in this folder or it's subfolders. Background We run Eclipse 3.6 and the m2eclipse plugin v0.10.2.20100623 manages our autobuild. For reasons beyond my

Tomcat throws ClassNotFound exceptions for classes in other open eclipse projects

北城以北 提交于 2019-11-27 00:29:52
问题 I have an eclipse project structure that looks something like this: eclipse project a project b All of these projects are Maven projects. Project B is an Eclipse WTP project and contains Project A as a dependency. I'm using the m2eclipse plugin. When I deploy Project B to Tomcat (all from within Eclipse) it always throws errors saying that it can't find classes from Project A. The only way I can resolve this is to close Project A in Eclipse and do a mvn install command, so at this point

How to update maven repository in Eclipse?

爷,独闯天下 提交于 2019-11-27 00:16:22
Assuming you're already using the m2eclipse plugin , what can you do it doesn't update the dependencies to the latest in your repo. For example, on the command line you can just add the -U flag as in: mvn clean install -U ...to force the dependencies to be updated. Is there something like this within Eclipse? (It doesn't always seem to pick up the latest updates.) You can right-click on your project then Maven > Update Snapshots . In newer versions of Eclipse that use the M2E plugin it is: Right-click on your project(s) --> Maven --> Update Project... In the following dialog is a checkbox for

m2e lifecycle-mapping not found

十年热恋 提交于 2019-11-27 00:09:01
I am trying to use the solution described here to solve the annoying "Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:build-helper-maven-plugin:1.7:add-source (execution: default, phase: generate-sources)" when I place the following plugin on my pom.xml: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin</artifactId> <executions> <execution> <phase>generate-sources</phase> <goals><goal>add-source</goal></goals> <configuration> <sources> <source>src/bootstrap/java</source> </sources> </configuration> </execution> </executions> </plugin

Missing Maven dependencies in Eclipse project

▼魔方 西西 提交于 2019-11-26 23:23:33
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 the project with some other computer (where project works fine), I notice that there are quite a few

Eclipse JVM configuration

旧城冷巷雨未停 提交于 2019-11-26 22:57:30
问题 Background: I've got a new eclipse installation and have installed the m2eclipse plugin. After startup m2eclipse generates the message: Eclipse is running in a JRE, but a JDK is required Following the instructions from here I've changed the eclipse.ini file to use the JDK JVM: -startup plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519 -product org.eclipse.epp.package.jee.product --launcher

maven-dependency-plugin (goals “copy-dependencies”, “unpack”) is not supported by m2e

試著忘記壹切 提交于 2019-11-26 22:19:20
问题 I have a fairly simple Maven project: <project> <dependencies> ... </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.4</version> <executions> <execution> <id>copy-dependencies</id> <phase>package</phase> <goals> <goal>copy-dependencies</goal> </goals> <configuration> <outputDirectory>${project.build.directory}/dependencies</outputDirectory> </configuration> </execution> </executions> </plugin> <

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

你离开我真会死。 提交于 2019-11-26 22:19:15
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:RELEASE: Could not find metadata org.apache.maven.archetypes:maven-archetype- webapp/maven-metadata.xml

Maven2: Missing artifact but jars are in place

江枫思渺然 提交于 2019-11-26 22:13:47
问题 From now to then, my Maven 2 started to mess around. I am using SPring STS 2.6.1 and have a single project based on Spring 3, Hibernate, DWR, Cometd and all that stuff. Today I just updated from Git und all of a sudden, I got that scary mvn exclamation mark (!) next to my project. After hitting "Project -> Maven -> Update dependencies" I just receive: 24.05.11 15:26:58 MESZ: Missing artifact org.jdom:jdom:jar:1.1:compile 24.05.11 15:26:58 MESZ: Missing artifact org.apache.solr:solr-common:jar