This is a maven error. It says that it is expecting a web.xml file in your project because it is a web application, as indicated by <packaging>war</packaging>. However, for recent web applications a web.xml file is totally optional. Maven needs to catch up to this convention. Add this to your maven pom.xml to let maven … Read more
This is the new behaviour of m2e (which replaced the old m2eclipse plugin). To specify what eclipse should do with the plugin you have to configure the build lifecycle mapping in the project’s pom.xml – or install a connector (which decides if the plugin needs to be executed in an eclipse build or not) if … Read more
In the project preferences it is possible to configure a lifecycle mapping. But for some reason I can only add custom goals to “after clean” and “on resource changed”. When I add the “compile” goal to the “resource changed” lifecycle mapping, then the JavaScript files are compiled when I change a resource. So I could … Read more
Assume you have two or more projects in your workspace e.g. project1, project2 and so on. If project1 is dependent on project2 and project3, you just need to define the dependency of project1 on project2 and project3. By enabling Resolve Workspace Artifacts, m2Eclipse will auto-build the SNAPSHOT JAR of project2 and project3 and add in … Read more
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.
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>
It seems to be a known issue. You can instruct m2e to ignore this. Option 1: pom.xml Add the following inside your <build/> tag: <pluginManagement> <plugins> <!– Ignore/Execute plugin execution –> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <!– copy-dependency plugin –> <pluginExecution> <pluginExecutionFilter> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <versionRange>[1.0.0,)</versionRange> <goals> <goal>copy-dependencies</goal> </goals> </pluginExecutionFilter> <action> <ignore /> </action> … Read more
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
If you right-click on your project, there should be an option under “maven” to “enable dependency management”. That’s it.
Seems your settings.xml file is missing your .m2 (local maven repo) folder. When using eclipse navigate to Window -> Preferences -> Maven -> User Settings -> Browse to your settings.xml and click apply. Then do maven Update Project.