Affan was correct. The connectors are all still there in Indigo, just hidden a little. Start Eclipse and open preferences. Find the Maven group and expand it. Select the “Discovery” item and click “Open Catalog”. A dialog will pop up with all the goodies. The connectors are at the bottom.
I encountered a similar problem and resolved it by moving the folder into my project folder. I then went to: Project > Properties > Resource > Resource Filters > Add… Set Filter type = Exclude all. Set Applies to = Folders. Set File and Folder Attributes = { Name, matches, < your_folder_name > }
All of the answers above may work for the time being but whenever you run maven on the command line or Maven → Update project… the JDK will be reset, this was also the question as I understand it. To fix this for good add the following code to your pom file. Remember to do … Read more
I had to do it slightly different to work for me: rightclick project, remove maven nature (or in newer eclipse, “Maven->Disable Maven Nature”) mvn eclipse:clean (with project open in eclipse/STS) delete the project in eclipse (but do not delete the sources) Import existing Maven project
My team works around this problem by wrapping the relevant configuration in a profile: <profile> <id>only-eclipse</id> <activation> <property> <name>m2e.version</name> </property> </activation> <build> <pluginManagement> <plugins> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> … </configuration> </plugin> </plugins> </pluginManagement> </build> </profile>
I had same problem with Eclipse 3.7.2 (Indigo) and maven 3.0.4. In my case, the problem was caused by missing maven-resources-plugin-2.4.3.jar in {user.home}\.m2\repository\org\apache\maven\plugins\maven-resources-plugin\2.4.3 folder. (no idea why maven didn’t update it) Solution: 1.) add dependency to pom.xml <dependency> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-resources-plugin</artifactId> <version>2.4.3</version> </dependency> 2.) run mvn install from Eclipse or from command line 3.) refresh the … Read more
Did you check your Project Properties -> Project Facets panel? (From that post) A WTP project is composed of multiple units of functionality (known as facets). The Java facet version needs to always match the java compiler compliance level. The best way to change java level is to use the Project Facets properties panel as … Read more
Simply create a java directory under main (i.e. src/main/java) and right-click on your project and select Maven > Update Project Configuration.
Indeed IDEs often cache the local repository (Eclipse does something similar, and I have to relaunch Eclipse). One ugly maven behavior you might encounter is that if you declare a dependency before you actually install it, maven will create an empty version of the missing dependency (folder with metadata but no jar), and you will … Read more
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