ebundle:updateconfig

Prepares Eclipse project configuration files for eclipse plugin development.

Parameters for the goal:

Parameter Type Expression Default Value Description
createLibLinks (Optional) boolean ${updateconfig.createLibLinks} false If true then .project file is modified to contain linked resource definition for each dependency, in the libDirectory directory. This allows dependent plugins to use plugin's dependent libraries. Defaults to false - subclipse does not yet support linked resources.
dependencies Set - ${project.artifacts} The set of dependencies required by project.
filterArchBundles (Optional) boolean ${updateconfig.filterArchBundles} true If true then all system-dependent bundles are filtered out from the dependency bundles. If false then bundles such as org.eclipse.swt.gtk.linux.x86_64 are copied from POM dependency list to the MANIFEST.MF file.
jarClasses boolean ${updateconfig.jarClasses} true Controls whether the compiled class files will be present in your plugin as a standard directory tree (false, use when creating a single-jar plugin), or the compiled class files will be zipped into a single jar file (true). Defaults to true.
jarFileName (Optional) String ${updateconfig.jarClassName} ${project.artifactId}-${project.version}.jar If jarClasses is true then this property contains the name of the jar file where the plugin classes are zipped.
libDirectory (Optional) String ${updateconfig.libDirectory} lib Defines where the jar dependencies will be placed when the plugin is assembled. Defaults to lib.
project MavenProject - ${project} Project instance, used to add new source directory to the build.