Generating Debian source packages for Eclipse plugins

This page describes the vision of the plugeclipse toolset.

The process consists of several steps. Firstly, the input (upstream) artifacts are analyzed in order to find determine target binary packages, and extract information from the input like license, package names, versions, descriptions, etc. During the second step, input artifacts are packed in the appropriate way and put into the source package.

Source artifactis

The possible upstream input artifacts:

• directory with several Eclipse features and plugins projects.
• update site with binary plugins and features plus Eclipse source plugin.
• sources in some form and custom build script.
• update site with binary plugins and features.

Only first three are "true" sources. Currently, only the last case is supported.

Build step

The following build steps are possible for input artifacts mentioned (in the same order as in the list above):

• building projects with Eclipse headless build (consider pdebuild, #22).
• replacing the binary jars with the jars built from the sources provided in the source plugin (consider the pdebuild too, source tree and build.properties will be dynamically created).
• building with custom Ant script.
• build not required - plugins are already in required form.