Support same launcher architecture as bndtools

[pkriens]

bndtools uses a slightly different launcher architecture than bnd. In the end they must be the same so ant launches the same thing as Eclipse.

[pkriens]

This is implemented in master now. Project now has getProjectTester and getProjectLauncher. By default they return the handlers for biz.aQute.launcher and biz.aQute.junit. These can be used as examples. You can add your own jars on the -runpath (for the launcher) and -testpath (for the tester). If such a JAR has a manifest header specifying the Tester-Plugin or Launcher-Plugin then an instance of the given class is made. This instance should extend ProjectLauncher or ProjectTester. This instance can then setup the classpath, vm args, etc.

Simplest config is:

-runpath: org.apache.felix.main

The ProjectLauncher and ProjectTester base classes specify an API to control the launching. They can be used by Eclipse (e.g.) to get the VM args, classpath, etc. to obtain the settings needed in the Eclipse launcher architecture. However, the launcher and tester can work independently from this, the launcher implements a launch method and the tester implements a test method that will launch a new VM properly setup.

[njbartlett]

Implemented in bndtools