Required Parameters

When set to false, the plugin will not create sub-projects and
instead reference those sub-projects using the installed package in
the local repositoryDefault value is: true.User property is: eclipse.useProjectReferences.

Optional Parameters

If set to true, the groupId of the artifact is
appended to the name of the generated Eclipse project. See
projectNameTemplate for other options.Default value is: false.User property is: eclipse.addGroupIdToProjectName.

If set to true, the version number of the artifact is
appended to the name of the generated Eclipse project. See
projectNameTemplate for other options.Default value is: false.User property is: eclipse.addVersionToProjectName.

The version of AJDT for which configuration files will be
generated. The default value is "1.5", supported versions are
"none" (AJDT support disabled), "1.4", and "1.5".Default value is: none.User property is: eclipse.ajdtVersion.

List of eclipse build commands. By default the
org.eclipse.jdt.core.javabuilder builder plus the
needed WTP builders are added. If you specify any configuration for
this parameter, only those buildcommands specified will be used;
the defaults won't be added. Use the
additionalBuildCommands parameter for that.
Configuration example: Old style:

Put classpath container entries last in eclipse classpath
configuration. Note that this behaviour, although useful in
situations were you want to override resources found in classpath
containers, will made JRE classes loaded after 3rd party jars, so
enabling it is not suggested.Default value is: false.User property is: eclipse.classpathContainersLast.

Enables/disables the downloading of javadoc attachments. Defaults
to false. When this flag is true remote repositories
are checked for javadocs: in order to avoid repeated check for
unavailable javadoc archives, a status cache is mantained. With
versions 2.6+ of the plugin to reset this cache run mvn
eclipse:remove-cache, or use the forceRecheck
option with versions. With older versions delete the file
mvn-eclipse-cache.properties in the target directory.User property is: downloadJavadocs.

Enables/disables the downloading of source attachments. Defaults to
false. When this flag is true remote repositories are
checked for sources: in order to avoid repeated check for
unavailable source archives, a status cache is mantained. With
versions 2.6+ of the plugin to reset this cache run mvn
eclipse:remove-cache, or use the forceRecheck
option with versions. With older versions delete the file
mvn-eclipse-cache.properties in the target directory.User property is: downloadSources.

Enables/disables the rechecking of the remote repository for
downloading source/javadoc attachments. Defaults to false. When
this flag is true and the source or javadoc attachment
has a status cache to indicate that it is not available, then the
remote repository will be rechecked for a source or javadoc
attachment and the status cache updated to reflect the new state.User property is: forceRecheck.

Limit the use of project references to the current workspace. No
project references will be created to projects in the reactor when
they are not available in the workspace.Default value is: false.User property is: eclipse.limitProjectReferencesToWorkspace.

If set to true, the standard execution environment
matching the compiler settings is set as JRE. If set to
false, the JRE matching the configured compiler-plugin
executable or JAVA_HOME is selected by name, if it is configured in
the workspace.Default value is: false.User property is: eclipse.preferStandardClasspathContainer.

Allows configuring the name of the eclipse projects. This property
if set wins over addVersionToProjectName and
addGroupIdToProjectName You can use [groupId],
[artifactId] and [version] variables. eg.
[groupId].[artifactId]-[version]User property is: eclipse.projectNameTemplate.

Whether to place test resources after main resources. Note that the
default behavior of Maven version 2.0.8 or later is to have test
dirs before main dirs in classpath so this is discouraged if you
need to reproduce the maven behavior during tests. The default
behavior is also changed in eclipse plugin version 2.6 in order to
better match the maven one. Switching to "test source last" can
anyway be useful if you need to run your application in eclipse,
since there is no concept in eclipse of "phases" with different set
of source dirs and dependencies like we have in maven.Default value is: false.User property is: eclipse.testSourcesLast.

This eclipse workspace is read and all artifacts detected there
will be connected as eclipse projects and will not be linked to the
jars in the local repository. Requirement is that it was created
with the similar wtp settings as the reactor projects, but the
project name template my differ. The pom's in the workspace
projects may not contain variables in the artefactId, groupId and
version tags. If workspace is not defined, then an attempt to
locate it by checking up the directory hierarchy will be made.User property is: eclipse.workspace.

The version of WTP for which configuration files will be generated.
The default value is "none" (don't generate WTP configuration),
supported versions are "R7", "1.0", "1.5" and "2.0"Default value is: none.User property is: wtpversion.

List of eclipse build commands. By default the
org.eclipse.jdt.core.javabuilder builder plus the
needed WTP builders are added. If you specify any configuration for
this parameter, only those buildcommands specified will be used;
the defaults won't be added. Use the
additionalBuildCommands parameter for that.
Configuration example: Old style:

Put classpath container entries last in eclipse classpath
configuration. Note that this behaviour, although useful in
situations were you want to override resources found in classpath
containers, will made JRE classes loaded after 3rd party jars, so
enabling it is not suggested.

Enables/disables the downloading of javadoc attachments. Defaults
to false. When this flag is true remote repositories
are checked for javadocs: in order to avoid repeated check for
unavailable javadoc archives, a status cache is mantained. With
versions 2.6+ of the plugin to reset this cache run mvn
eclipse:remove-cache, or use the forceRecheck
option with versions. With older versions delete the file
mvn-eclipse-cache.properties in the target directory.

Enables/disables the downloading of source attachments. Defaults to
false. When this flag is true remote repositories are
checked for sources: in order to avoid repeated check for
unavailable source archives, a status cache is mantained. With
versions 2.6+ of the plugin to reset this cache run mvn
eclipse:remove-cache, or use the forceRecheck
option with versions. With older versions delete the file
mvn-eclipse-cache.properties in the target directory.

Enables/disables the rechecking of the remote repository for
downloading source/javadoc attachments. Defaults to false. When
this flag is true and the source or javadoc attachment
has a status cache to indicate that it is not available, then the
remote repository will be rechecked for a source or javadoc
attachment and the status cache updated to reflect the new state.

If set to true, the standard execution environment
matching the compiler settings is set as JRE. If set to
false, the JRE matching the configured compiler-plugin
executable or JAVA_HOME is selected by name, if it is configured in
the workspace.

Allows configuring the name of the eclipse projects. This property
if set wins over addVersionToProjectName and
addGroupIdToProjectName You can use [groupId],
[artifactId] and [version] variables. eg.
[groupId].[artifactId]-[version]

Whether to place test resources after main resources. Note that the
default behavior of Maven version 2.0.8 or later is to have test
dirs before main dirs in classpath so this is discouraged if you
need to reproduce the maven behavior during tests. The default
behavior is also changed in eclipse plugin version 2.6 in order to
better match the maven one. Switching to "test source last" can
anyway be useful if you need to run your application in eclipse,
since there is no concept in eclipse of "phases" with different set
of source dirs and dependencies like we have in maven.

This eclipse workspace is read and all artifacts detected there
will be connected as eclipse projects and will not be linked to the
jars in the local repository. Requirement is that it was created
with the similar wtp settings as the reactor projects, but the
project name template my differ. The pom's in the workspace
projects may not contain variables in the artefactId, groupId and
version tags. If workspace is not defined, then an attempt to
locate it by checking up the directory hierarchy will be made.