Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 323752

Summary:	Make it easier to export SDKs
Product:	[Eclipse Project] PDE	Reporter:	Jeff McAffer <jeffmcaffer>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	aniefer, pwebster
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Jeff McAffer

2010-08-26 15:53:21 EDT

The Eclipse community finds if very useful to have an SDK (e.g., binary + source) for the thing they are developing or developing against. Unfortunately, the workflow for making these SDKs is not easy.

- PDE UI offers the ability to Generate Source Bundles on product export but this seems only to include in the output source for bundles which were actually compiled. Consumers of an SDK likely would want all the source that is available.

- PDE Build has facilities for generating source bundles but as I recall we had to great template source features or something to ensure that source was created and associated with the product. (that one is a little fuzzy and may have improved)

- The metadata for a product build would ideally contain top level feature that would be the source for the product.  Then consumers could add this to their target to get source.

I'm starting this off in PDE UI but there likely are some things that need to be done in Build as well.

Comment 1 Jeff McAffer

2010-10-31 12:30:48 EDT

See Bug 329162 and bug 328929.  Those make it easier to generate source bundles and get them into your target (respectively).  Those may actually be enough to solve the problem raised in this bug but I suspect there will still be some integration effort.  For example, will PDE UI surface the proposed new PDE Build source generation function?

Comment 2 Eclipse Webmaster

2019-09-06 16:18:15 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 3 Julian Honnen

2019-09-09 02:32:41 EDT

Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.