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

Bug 253958

Summary:	build.properties editor should have UI to set output.<library>
Product:	[Eclipse Project] PDE	Reporter:	Markus Keller <markus.kell.r>
Component:	UI	Assignee:	Chris Aniszczyk <caniszczyk>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	aniefer, ankur_sharma, caniszczyk, curtis.windatt.public, darin.eclipse
Version:	3.5
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Markus Keller

2008-11-05 12:03:15 EST

I20081104-0916

Follow-up to bug 253950.

The "Build" tab of the PDE manifest editor should have UI to set the output.<lib> property for each source.<lib>.

Comment 1 Chris Aniszczyk

2008-11-11 19:48:17 EST

Andrew, if we have something like "source.." listed... is output.. inferred automatically? I'm curious how PDE Build handles this today.

Once I have a better understand of things, I'll work on getting the UI perfected.

Anything to keep Markus happy :)

Comment 2 Darin Wright

2008-11-21 13:57:22 EST

I'm not sure we want to expose this. The output library for a source folder is defined by the Java build path. If we expose this in the editor, it will have update the project's build path - I think it would be better to infer it from the build path rather than let it be editable in this editor. Is there a reason you want edit it? 

I'd rather just have a way to synchronize build.properties with the build path.

Comment 3 Darin Wright

2008-11-21 16:08:20 EST

Based on the comments in bug 253950, I think we should close this one as WONTFIX.

Comment 4 Markus Keller

2008-11-21 20:06:21 EST

If you can pass this behind the scenes that's even better. Closing as wontfix.

Comment 5 Markus Keller

2009-11-30 06:55:57 EST

Bug 253950 has been resolved differently, so we need this UI again.

Plus UI for bug 154292.

Comment 6 Eclipse Webmaster

2019-09-06 16:18:19 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 7 Julian Honnen

2019-09-09 02:38:27 EDT

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