Generates the rad-6 configuration files.
Mojo Attributes :
generate-resources prior to executing itself.| Name | Type | Description |
|---|---|---|
| buildOutputDirectory | File |
The default output directory Default value is ${project.build.outputDirectory}. |
| useProjectReferences | boolean |
When set to false, the plugin will not create sub-projects and instead
reference those sub-projects using the installed package in the local
repository Default value is true. |
| Name | Type | Description |
|---|---|---|
| addGroupIdToProjectName | boolean |
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. |
| addVersionToProjectName | boolean |
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. |
| additionalBuildcommands | List |
List of eclipse build commands to be added to the default ones.
Old style:
<additionalBuildcommands> <buildcommand>org.springframework.ide.eclipse.core.springbuilder</buildcommand> </additionalBuildcommands>New style: <additionalBuildcommands> <buildCommand> <name>org.ui.externaltools.ExternalToolBuilder</name> <triggers>auto,full,incremental,</triggers> <arguments> <LaunchConfigHandle><project>./externalToolBuilders/MavenBuilder.launch</LaunchConfighandle> </arguments> </buildCommand> </additionalBuildcommands>Note the difference between buildcommand
and buildCommand.
You can mix and match old and new-style configuration entries. |
| additionalConfig | EclipseConfigFile[] |
Allow to configure additional generic configuration files for eclipse that will be written out to disk when
running eclipse:eclipse. FOr each file you can specify the name and the text content.
<additionalConfig> <file> <name>.checkstyle</name> <content> <![CDATA[<fileset-config file-format-version="1.2.0" simple-config="true"> <fileset name="all" enabled="true" check-config-name="acme corporate style" local="false"> <file-match-pattern match-pattern="." include-pattern="true"/> </fileset> <filter name="NonSrcDirs" enabled="true"/> </fileset-config>]]> </content> </file> </additionalConfig> |
| additionalProjectFacets | Map |
List of eclipse project facets to be added to the default ones.
<additionalProjectFacets> <jst.jsf>1.1<jst.jsf/> </additionalProjectFacets> |
| additionalProjectnatures | List |
List of eclipse project natures to be added to the default ones.
<additionalProjectnatures> <projectnature>org.springframework.ide.eclipse.core.springnature</projectnature> </additionalProjectnatures> |
| artifactCollector | ArtifactCollector |
Artifact collector, needed to resolve dependencies. |
| artifactFactory | ArtifactFactory |
Artifact factory, needed to download source jars for inclusion in classpath. |
| artifactMetadataSource | ArtifactMetadataSource |
No description. |
| artifactResolver | ArtifactResolver |
Artifact resolver, needed to download source jars for inclusion in classpath. |
| buildcommands | List |
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:
<buildcommands> <buildcommand>org.eclipse.wst.common.modulecore.ComponentStructuralBuilder</buildcommand> <buildcommand>org.eclipse.jdt.core.javabuilder</buildcommand> <buildcommand>org.eclipse.wst.common.modulecore.ComponentStructuralBuilderDependencyResolver</buildcommand> </buildcommands>For new style, see additionalBuildCommands. |
| classpathContainers | List |
List of container classpath entries. By default the org.eclipse.jdt.launching.JRE_CONTAINER classpath
container is added. Configuration example:
<classpathContainers> <classpathContainer>org.eclipse.jdt.launching.JRE_CONTAINER</classpathContainer> <classpathContainer>org.eclipse.jst.server.core.container/org.eclipse.jst.server.tomcat.runtimeTarget/Apache Tomcat v5.5</classpathContainer> <classpathContainer>org.eclipse.jst.j2ee.internal.web.container/artifact</classpathContainer> </classpathContainers> |
| downloadJavadocs | boolean |
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 into the target dir of the root project.
Run mvn:clean or delete the file
mvn-eclipse-cache.properties in order
to reset this cache. |
| downloadSources | boolean |
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 into the target dir of the root project. Run mvn:clean or delete the
file mvn-eclipse-cache.properties in order to reset this cache. |
| eclipseDownloadSources | boolean |
Enables/disables the downloading of source attachments. Defaults to false. DEPRECATED - use downloadSources |
| eclipseProjectDir | File |
Eclipse workspace directory. |
| generatedResourceDirName | String |
Use this to specify a different generated resources folder than
target/generated-resources/rad6.
Set to "none" to skip this folder generation. Default value is target/generated-resources/rad6. |
| manifest | File |
The relative path of the manifest file Default value is ${basedir}/META-INF/MANIFEST.MF. |
| pde | boolean |
Is it an PDE project? If yes, the plugin adds the necessary natures and build commands to
the .project file. Additionally it copies all libraries to a project local directory and
references them instead of referencing the files in the local Maven repository. It also
ensured that the "Bundle-Classpath" in META-INF/MANIFEST.MF is synchronized. Default value is false. |
| projectNameTemplate | String |
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] |
| projectnatures | List |
List of eclipse project natures. By default the
org.eclipse.jdt.core.javanature nature plus the needed WTP
natures are added. Natures added using this property replace the default list.
<projectnatures> <projectnature>org.eclipse.jdt.core.javanature</projectnature> <projectnature>org.eclipse.wst.common.modulecore.ModuleCoreNature</projectnature> </projectnatures> |
| skip | boolean |
Skip the operation when true. Default value is false. |
| warContextRoot | String |
The context root of the webapplication. This parameter is only used when the current project is a war project, else it will be ignored. |
| wtpContextName | String |
JEE context name of the WTP module. ( ex. WEB context name ). Default value is ${project.artifactId}. |
| wtpversion | String |
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", and "1.5" Default value is none. |
If set to true, the groupId of the artifact is appended
to the name of the generated Eclipse project. See projectNameTemplate for other options.
booleanNo${eclipse.addGroupIdToProjectName}falseIf set to true, the version number of the artifact is appended
to the name of the generated Eclipse project. See projectNameTemplate for other options.
booleanNo${eclipse.addVersionToProjectName}falseList of eclipse build commands to be added to the default ones. Old style:
<additionalBuildcommands> <buildcommand>org.springframework.ide.eclipse.core.springbuilder</buildcommand> </additionalBuildcommands>New style:
<additionalBuildcommands> <buildCommand> <name>org.ui.externaltools.ExternalToolBuilder</name> <triggers>auto,full,incremental,</triggers> <arguments> <LaunchConfigHandle><project>./externalToolBuilders/MavenBuilder.launch</LaunchConfighandle> </arguments> </buildCommand> </additionalBuildcommands>Note the difference between
buildcommand
and buildCommand.
You can mix and match old and new-style configuration entries.
java.util.ListNoAllow to configure additional generic configuration files for eclipse that will be written out to disk when running eclipse:eclipse. FOr each file you can specify the name and the text content.
<additionalConfig> <file> <name>.checkstyle</name> <content> <![CDATA[<fileset-config file-format-version="1.2.0" simple-config="true"> <fileset name="all" enabled="true" check-config-name="acme corporate style" local="false"> <file-match-pattern match-pattern="." include-pattern="true"/> </fileset> <filter name="NonSrcDirs" enabled="true"/> </fileset-config>]]> </content> </file> </additionalConfig>
org.apache.maven.plugin.eclipse.EclipseConfigFile[]NoList of eclipse project facets to be added to the default ones.
<additionalProjectFacets> <jst.jsf>1.1<jst.jsf/> </additionalProjectFacets>
java.util.MapNoList of eclipse project natures to be added to the default ones.
<additionalProjectnatures> <projectnature>org.springframework.ide.eclipse.core.springnature</projectnature> </additionalProjectnatures>
java.util.ListNoArtifact collector, needed to resolve dependencies.
org.apache.maven.artifact.resolver.ArtifactCollectorNoArtifact factory, needed to download source jars for inclusion in classpath.
org.apache.maven.artifact.factory.ArtifactFactoryNoNo Description.
org.apache.maven.artifact.metadata.ArtifactMetadataSourceNoArtifact resolver, needed to download source jars for inclusion in classpath.
org.apache.maven.artifact.resolver.ArtifactResolverNoThe default output directory
java.io.FileYes${outputDirectory}${project.build.outputDirectory}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:
<buildcommands> <buildcommand>org.eclipse.wst.common.modulecore.ComponentStructuralBuilder</buildcommand> <buildcommand>org.eclipse.jdt.core.javabuilder</buildcommand> <buildcommand>org.eclipse.wst.common.modulecore.ComponentStructuralBuilderDependencyResolver</buildcommand> </buildcommands>For new style, see
additionalBuildCommands.
java.util.ListNoList of container classpath entries. By default the org.eclipse.jdt.launching.JRE_CONTAINER classpath
container is added. Configuration example:
<classpathContainers> <classpathContainer>org.eclipse.jdt.launching.JRE_CONTAINER</classpathContainer> <classpathContainer>org.eclipse.jst.server.core.container/org.eclipse.jst.server.tomcat.runtimeTarget/Apache Tomcat v5.5</classpathContainer> <classpathContainer>org.eclipse.jst.j2ee.internal.web.container/artifact</classpathContainer> </classpathContainers>
java.util.ListNoEnables/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 into the target dir of the root project.
Run mvn:clean or delete the file
mvn-eclipse-cache.properties in order
to reset this cache.
booleanNo${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 into the target dir of the root project. Run mvn:clean or delete the
file mvn-eclipse-cache.properties in order to reset this cache.
booleanNo${downloadSources}Enables/disables the downloading of source attachments. Defaults to false. DEPRECATED - use downloadSources
booleanNo${eclipse.downloadSources}Eclipse workspace directory.
java.io.FileNo${eclipse.workspace}Use this to specify a different generated resources folder than target/generated-resources/rad6. Set to "none" to skip this folder generation.
java.lang.StringNo${generatedResourceDirName}target/generated-resources/rad6The relative path of the manifest file
java.io.FileNo${eclipse.manifest}${basedir}/META-INF/MANIFEST.MFIs it an PDE project? If yes, the plugin adds the necessary natures and build commands to the .project file. Additionally it copies all libraries to a project local directory and references them instead of referencing the files in the local Maven repository. It also ensured that the "Bundle-Classpath" in META-INF/MANIFEST.MF is synchronized.
booleanNo${eclipse.pde}falseAllows 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]
java.lang.StringNo${eclipse.projectNameTemplate}List of eclipse project natures. By default the
org.eclipse.jdt.core.javanature nature plus the needed WTP
natures are added. Natures added using this property replace the default list.
<projectnatures> <projectnature>org.eclipse.jdt.core.javanature</projectnature> <projectnature>org.eclipse.wst.common.modulecore.ModuleCoreNature</projectnature> </projectnatures>
java.util.ListNoSkip the operation when true.
booleanNo${eclipse.skip}falseWhen set to false, the plugin will not create sub-projects and instead reference those sub-projects using the installed package in the local repository
booleanYes${eclipse.useProjectReferences}trueThe context root of the webapplication. This parameter is only used when the current project is a war project, else it will be ignored.
java.lang.StringNoJEE context name of the WTP module. ( ex. WEB context name ).
java.lang.StringNo${wtpContextName}${project.artifactId}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", and "1.5"
java.lang.StringNo${wtpversion}none