Community
Participate
Working Groups
3.2 RC1 I created a customized SDK for our company developers based on 3.2 RC1. However, when writing a tutorial I noticed that the execution environments were not available for simple Java projects. A little research showed that even such basic execution environments like J2SE-1.4 are defined in PDE core. A workaround is to include PDE core in my bundle. However, I'd like to see the execution environment definitions moved down to JDT. Otherwise it doesn't make sense if every client has to redefine it in it's own plug-ins.
Gunnar, what do you expect to be done on the PDE/UI side man?
(In reply to comment #1) > Gunnar, what do you expect to be done on the PDE/UI side man? Sorry, I couldn't classify better. There is not PDE core component. Should it be moved to JDT or Platform instead?
yes, please move to whoever component you feel should contribute these EE's. I'm not sure what that would be. jdt/debug? jdt/ui? jdt/core? it's all fuzzy right now. but a jdt component would be a good side, since there is nothing to be done on the pde side.
moving to jdt
moving to jdt core
moving to JDT debug
Deferred for post 3.2
Is it possible to expect fix for this bug in 3.2.2 or at least 3.3? Currently _regular_ (not plugins etc.) Java or J2EE projects created under Eclipse with PDE installed and utilising this new useful & _advertised_ "Execution environments" feature just break if imported into another Eclipse with JST/WST installed but without PDE (that is _not_ necessary for such projects).
This is fixed in 3.3 - the EE's are now contributed by JDT.
Fixed with bug 163444 *** This bug has been marked as a duplicate of bug 163444 ***