Community
Participate
Working Groups
Currently the prereqs for the DM toolkit plugins are set to other Eclipse 3.4 based plugins. With a change to the prereq expressions we can also enable Eclipse 3.3. The question going forward is whether we want to claim 3.3 support. The change is to just remove the "3.4" designation for the Eclipse base plugins in the list fo rthe common and j2ee plugins.
Friday or Monday I will try to recreate in Eclipse 3.4 the problems I've seen using the DM Toolkit on Eclipse 3.3.2 on Linux. If the problems are still there, I'll open them as regular bugs. If not, I will open them as bugs and make this bug depend on those.
Troy, if we change to support Eclipse 3.3, it will have to be a project wide decision. Can you remind me of the reason why you wanted to stay on 3.3 instead of moving to 3.4? We need to understand both the reasons to support 3.3 and to determine if we are dependent on 3.4 in any of our code.
There is no plan to provide support for eclipse 3.3.
Sorry I didn't respond to comment #2. It slipped through the inbox. The only reason I wanted Eclipse 3.3 support was that you told me you were pretty sure that the dependencies on 3.4 were probably not that significant, and you thought it might work under 3.3 with a minimum of effort. I'm fine with leaving the dependency on 3.4. Thanks.
Yeah, the only reason we won't go to the trouble of relaxing the version # restriction here is that it would be moot for this to work in 3.3 if the rest of COSMOS hasn't committed to support 3.3 for their code. And there are significant testing implications if we want to continue to allow 3.3 to work. We've been told Ganymede is our primary objective :-)
closing to cleanup bugzilla
