Eclipse Maven Plugin ![Maven Central](https://camo.githubusercontent.com/3fc89a5313f4ff524b0d1e257a891031c9734d06d01b16f9c110addd31a99df5/68747470733a2f2f6d6176656e2d6261646765732e6865726f6b756170702e636f6d2f6d6176656e2d63656e7472616c2f636f6d2e6769746875622e6d6172736368616c6c2f65636c697073652d6d6176656e2d706c7567696e2f62616467652e737667)
The Eclipse Plugin is used to generate Eclipse IDE files (.project, .classpath and the .settings folder) from a POM.
This is based on wcm-io-devops/eclipse-maven-plugin which is a fork of the original Maven Eclipse Plugin which was retired end of 2015 in favor of M2Eclipse.
For more information check out the generated plugin page .
Changes since the original Maven Eclipse Plugin 2.10
Added
- support for test folders
- support for test dependencies, both JAR and project dependencies
- support for the
--release
compiler option - ignore optional compile problems on attached source folders
- additional source folders
- JavaEE 7
- JavaEE 8
- Java 9 to 17
Removed
- all goals except
eclipse
andclean
- AJDT support
- MyEclipse support
- RAD support
To use this in your projects update all your POMs to use
<plugin>
<groupId>com.github.marschall</groupId>
<artifactId>eclipse-maven-plugin</artifactId>
<version>2.12.0</version>
</plugin>
instead of
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.10</version>
</plugin>
If you add com.github.marschall
as a pluginGroup to your ${user.home}/.m2/settings.xml
or ${maven.home}/conf/settings.xml
<pluginGroups>
<pluginGroup>com.github.marschall</pluginGroup>
</pluginGroups>
you will be able to use eclipse:eclipse
as a Maven goal directly.