Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351415 - Installing JSDT feature into RCP drags in JDT debug/core
Summary: Installing JSDT feature into RCP drags in JDT debug/core
Status: CLOSED DUPLICATE of bug 350438
Alias: None
Product: JSDT
Classification: WebTools
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Nitin Dahyabhai CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-07 06:24 EDT by Alex Blewitt CLA
Modified: 2011-07-07 10:10 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Blewitt CLA 2011-07-07 06:24:52 EDT 
From a basic RCP with P2 capabilities, if I install the org.eclipse.wst.jsdt.feature(.feature.group), it drags in plugins 
org.eclipse.jdt.debug 
org.eclipse.jdt.core 
org.eclipse.jdt.launching 

Is this necessary/desirable? I can't see where it needs JDT, though if it does please file this as invalid.
Comment 1 Michael Rennie CLA 2011-07-07 10:10:37 EDT 
(In reply to comment #0)
> Is this necessary/desirable? I can't see where it needs JDT, though if it does
> please file this as invalid.

In its current shape the debug support for Rhino in JSDT debug makes use of the VM tools from the jdt.launching, and sadly, jdt.launching has a dep on jdt.debug, which in turn has a dep on jdt.core.

This is a dupe of bug 350438, where we are planning to investigate splitting up jdt.launching (or creating our own VM support tools) so that VM related support can be used without all the extra overhead.

*** This bug has been marked as a duplicate of bug 350438 ***