Bug 346329 - SDK-only build
Summary: SDK-only build
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-18 15:43 EDT by Matt Heitz CLA
Modified: 2017-02-23 14:20 EST (History)
0 users

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 Matt Heitz CLA 2011-05-18 15:43:22 EDT 
As an EGL tool developer, I need a build of the EDT code that only includes the SDK, not the IDE, so that I can plug my EDT-based tool into RBD.

We need to decide how an SDK build is packaged.  Do we copy everything into one big jar, or let people download the plugins they need and provide an easy way to put all those jars into their classpath?  Maybe make one jar for the compiler and one for each generator.

Some refactoring needs to be done before an SDK build is possible.  As of today (4/19/2011) several of the plugins needed for EDT SDK have dependencies on Eclipse plugins that won't be present when we're not running as plugins within the workbench.  For example, org.eclipse.edt.gen and org.eclipse.edt.mof.egl depend on org.eclipse.core.resources for their Plugin classes.  That's not a problem if their Plugin classes aren't required for SDK, but we need to look into it.  More significantly, org.eclipse.edt.compiler depends on org.eclipse.ui and org.eclipse.jface, among others.  Those dependencies must either be moved to one of the IDE plugins or deleted (I see at least one class for VAGen compatility, which should go away).