These linked resources appear in the root directory of your PDE project, and link the jars within your repository into the root of your project as required by Eclipse.

When PDE mode is enabled, dependencies are configured as Eclipse linked resources instead.Įclipse linked resources work like symbolic links within the Eclipse IDE. In order for the Eclipse PDE system to build or deploy an Eclipse PDE project, it requires that dependent jars exist somewhere within the project itself.īy default, the eclipse:eclipse goal sets up the Eclipse classpath such that the project depends on jars in the external local maven repository. This Eclipse library resolves Eclipse/OSGI dependencies, and removes the need for maven to depend explicitly on eclipse jars. The Plugin Dependencies library is added to the Eclipse classpath. The is added to the list of eclipse project natures, indicating to Eclipse that this project is a PDE project. These might be set in the build file by the property task, or might be set outside Ant.ĭynamic or configurable build properties (such as path names or version numbers) are often handled through the use of a properties file associated with the Ant build file (often named build.properties).When PDE support is enabled in the maven-eclipse-plugin, the Eclipse project files are configured differently to the default. Instead of a model extended with shell-based commands, Ant is extended using Java classes.Įach task is run by an object that implements a particular task interface.Īnt build files are written in XML (and have the default name build.xml).Įach build file contains one project and at least one (default) target.Įach task element of the build file can have an id attribute and can later be referred to by the value supplied to this. At runtime, a user can specify which Ant target(s) they want to run, and Ant will generate and execute tasks from a dependency tree built from the target(s).

Apache ant eclipse