[jdt-debug-dev] Milestone 6 plan

[Matt_Lavin@xxxxxxx]

I have a couple of questions about the changes to be made for milestone 6.

Improved support for default classpath & bootpath (delegate to VM installs) 
Would it be possible for the allow the default classpath and bootpath to be set by the TabGroup instead of the vm install?  If the java tab group delegates its responsibility for setting the defaults back to the vm install that is fine.  However, it would be nice if the tab group could set its own defaults.

Enhanced remote connection - support a dynamic set of launch arguments
What exactly does that mean?  What sort of launch arguements would be dynamic?

Re-organization of launch config tabs
Could somebody explain a little more about what this means.

Something that wasn't mentioned on the plan but I was expecting was to make the java launch tabs public.  I thought that somebody had mentioned that they would be moved to API some time.

"The Java tabs will be promoted to API, but they are not intended to be subclassed - only instantiated.  The classes will have public constructors, but all implementation will be considered internal and non-public. The reason for this is that the tabs are expected to change dramatically in the near term, as we receive user feedback. It is not possible to consider the tabs as stable API. Currently, the only inter-tab dependency is the notion of a "project" which is used to set default values (i.e. classpath). The tabs will use the launch configuration working copy mechanism to perform this communication. Creating a "java tab" framework is not something that we have time to do in the 2.0 release. "