1. Web Starter Kit: runtime
pre-packaged with equinox, p2, jetty
plugins/features managed via p2
dropins: bundles, web-application bundles
webapps: legacy J2EE web-applications
lib/ext: legacy J2EE shared libraries
launchers: native and cross-platform shell scripts
Produced from an eclipse build and published as eclipse products in the Helios repository.
Ready to be provisioned with additional features or bundles; for example add JPA by provisioning the EclipseLink feature.
p2: same setup than in the eclipse-platform but without UI;
support for robust management of the provisioning of the application. support for development situation with the dropins folder.
jetty: support for web-bundles and traditional J22 web-application; migration path from J2EE to OSGi.

2. Web Starter Kit: PDE integration... for Indigo?
Current integration to PDE:
dot project file
target platform definition
launch configuration
Possible Indigo work:
Extend the Target Platform provisioning to cover the launch configurations and root files.
Hide the provisioning of JUnit in the JUnit launcher
Extend the sources header for non PDE projects
Goal for the future integration: make the Starter Kit converge with the Target Provisoning in PDE:
Case 1: someone starts from PDE and provisions the Starter Kit. Get the features, bundles, launch configurations, root files, sources. Optionally the ability to view the files in the workspace.
Case 2: someone starts from a downloaded Starter Kit and needs to debug something or and some web-bundle thanks to PDE.
Use PDE to import the whole thing in as few steps as possible. Ability to add the sources and have JUnit ready.
Ideally Case 1 and Case 2 end up with the same set of files.

3. Target Platform: JUnit support for OSGi developers
Something available for many years to RCP developers.
Now ready for OSGi developers.
This screenshot might be slightly obsolete