All Classes and Interfaces
Class
Description
Common behaviours for creating or adapting the manifest files for eclipse environments.
Common functionality for both exploded and packaged plugins.
Abstract base plugin which takes care of the common stuff usually needed by maven IDE plugins.
Base class to hold common constants used by extending classes.
Represents a buildCommand section in the
.project file.Configures The following Eclipse Workspace features:
Adds the classpath variable MAVEN_REPO to Eclipse.
Optionally load Eclipse code style file via a URL.
Constants for supported language and project packaging
Writes an external ant launch file.
Writes eclipse .classpath file.
Deletes the .project, .classpath, .wtpmodules files and .settings folder used by Eclipse.
an Eclipse code style file
Represents a generic configuration file, with a name and a content.
Base class for writing external launch configuration files.
Create or adapt the manifest files for the RAD6 runtime dependencys. attention these will not be used for the real
ear these are just to get the runtime enviorment using the maven dependencies.
Abstraction of Eclipse plugins
Generates the following eclipse configuration files:
.project and .classpath files
.setting/org.eclipse.jdt.core.prefs with project specific compiler settings
various configuration files for WTP (Web Tools Project), if the parameter wtpversion is set to a
valid version (WTP configuration is not generated by default)
If this goal is run on a multiproject root, dependencies between modules will be configured as direct project
dependencies in Eclipse (unless useProjectReferences is set to false).Writes eclipse .project file.
Represent an eclipse source dir.
Add Eclipse artifacts from an Eclipse installation or a local P2 repo to the local Maven repo.
This writer creates the application.xml and the .modulemaps files for RAD6 the the META-INF directory in the project
root. this is where RAD6 requires the files to be.
Component writer for WTP 1.5.
Creates a .settings folder for Eclipse WTP 1.x release and writes out the configuration under it.
Creates a .settings folder for Eclipse WTP 1.x release and writes out the configuration under it.
Writes eclipse .wtpmodules file.
Represents an Eclipse plugin that it's exploded in a directory
Display help information on eclipse-maven-plugin.
Call
Call
mvn eclipse:help -Ddetail=true -Dgoal=<goal-name> to display parameter details.Install plugins resolved from the Maven repository system into an Eclipse instance.
Represents a LinkedResources section in the
.project file.Deletes configuration files used by MyEclipse
Writer for MyEclipse Hibernate Capability
MyEclipse .mymetadata configuration file writer
Generates MyEclipse configuration files
MyEclipse .springBeans configuration file writer
MyEclipse .mystrutsdata configuration file writer
Represents an Eclipse plugin that it's packaged as a jar
This writer creates the application.xml and the .modulemaps files for RAD6 in the META-INF directory in the project
root. this is where RAD6 requires the files to be.
Deletes the config files used by Rad-6. the files .j2ee and the file .websettings
Adapts the .classpath file for RAD6 for now write hardcoded: target/websphere/classes future releases could make this
varriable.
Creates the .j2ee file for RAD6 for now write hardcoded: EJB version 2.1 WAR version 2.4 EAR version 1.4 future
releases could make these varriable.
Copy all dependent jar in the directorys where RAD6 needs then to use the runtime enviorment in RAD6. so all
dependent jars in the EAR rootdirectory and all dependend jars in the WAR WEB-INF/lib directory
Create or adapt the manifest files for the RAD6 runtime dependencys. attention these will not be used for the real
ear these are just to get the runtime enviorment using the maven dependencies.
Generates the rad-6 configuration files.
Creates a .settings folder for Eclipse WTP 1.x release and writes out the configuration under it.
Creates a .settings folder for Eclipse WTP 1.x release and writes out the configuration under it.
Scan the eclipse workspace and create a array with
IdeDependency for all found artefacts.Removes the not-available marker files from the repository.
For all projects currently part of the workspace, all references to the
M2_REPO classpath variable are
resolved.