Bug 177637 - Should the jres be merged when multiple execution environments are specified
Summary: Should the jres be merged when multiple execution environments are specified
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-15 15:47 EDT by Pascal Rapicault CLA
Modified: 2022-11-17 14:29 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2007-03-15 15:47:30 EDT
Following discussions around https://bugs.eclipse.org/bugs/show_bug.cgi?id=177476 we were wondering if when multiple execution environments are specified, they should not all be merged to contribute to the compilation classpath. Also this merge would have to make sure that the smallest EE would be appear first on the classpath.
Comment 1 Jeff McAffer CLA 2007-03-15 17:07:10 EDT
In some cases merging is the right answer, in others intersecting is right.  For example, some bundle that optionally uses some JRE classes (NIO for example) needs to compile against 1.4+.  On the otherhand, a bundle that spec foudnation 1.0 and J2SE1.3 likely does not want to reference javax.microedition.*.

Just pointing this out.  in general anything that improves the accuracy and usefulness of the compile-time classpath is a good thing.
Comment 2 Lars Vogel CLA 2018-12-03 09:10:27 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 3 Lars Vogel CLA 2018-12-03 09:13:56 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 4 Eclipse Genie CLA 2020-11-26 15:30:38 EST
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.

--
The automated Eclipse Genie.
Comment 5 Eclipse Genie CLA 2022-11-17 14:29:38 EST
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.

--
The automated Eclipse Genie.