|
It is no big deal really. I can run both WDSC and Eclipse 3.2 with the MyEclipse plugin in separate workspaces. It would just be nice to have one place to go rather than two.
Pete Kushal Munir wrote:
Hi Pete, The current version of WDSC, 6.0.1, will not support Eclipse 3.2. In fact, it won't support anything above Eclipse 3.0.x since there have been a number of major changes to Eclipse since the 3.0 release. Unfortunately, this means that you will have to wait for a new version of WDSC for a newer version of Eclipse to be supported. Cheers, Kushal Munir Websphere Development Studio Client for iSeries IBM Toronto Lab, 8200 Warden Ave., Markham, ON Phone: (905) 413-3118 Tie-Line: 969-3118 Email: kmunir@xxxxxxxxxxPete Helgren <Pete@xxxxxxxxxx> Sent by: To wdsci-l-bounces@m Websphere Development Studio Client idrange.com for iSeries <wdsci-l@xxxxxxxxxxxx> cc 08/21/2006 04:40 Subject PM Re: [WDSCI-L] Eclipse 3.2 support Please respond to Websphere Development Studio Client for iSeries <wdsci-l@midrange .com>On the Eclipse 3.2 stuff, I can't remember exactly who it was at the WDSC kiosk at Common I talked to, but I think I was pretty clear on my need to get to 3.2 (it might have been Davis but my days at Common get to be a blur sometimes...not sure if she was a Spring Common). Originally I was looking at getting WDSC to 3.1.2 for my Eclipse so I could run MyEclipse but the WDSC folks said 3.2 was a more likely version. I honestly haven't done a side by side comparison of MyEclipse 5.0 and WDSC. I was impressed with the Matisse implementation but I should probably try some Swing development with WDSC. We use Hibernate and MyEclipse 5.0 has some enhanced support for that. Finally, the Javascript debugging was supposed to be improved in MyEclipse 5.0 (using Eclipse 3.2). Internally we have standardized on MyEclipse and there are probably only 3 developers who routinely move between Java and RPG. The Java folks use MyEclipse, the RPG folks use SEU (but are moving to WDSC) so I guess we could theoretically move our Java folks to WDSC if WDSC covers all the MyEclipse functionality. I'll look into that and get a "sales pitch" ready. Maybe I'll have one of the more experienced Java folks try WDSC and see what they have to say. Pete Joe Pluta wrote:Pete, who told you this? I have never been led to believe that WDSC willbeconcurrent with Eclipse. There's simply too much going on in thepackage.I can ask around, but I haven't heard any timeframe for WDSC to bereleasedon 3.2 of Eclipse. Man, I'm frightened to think what kind of upgradethatwould be! Also, why do you use MyEclipse rather than WDSC? WDSC has a complete integrated toolset for developing web applications, including the besttestenvironment capabilities of any IDE. JoeFrom: Pete Helgren I have been running two Eclipse environments for quite some time and I am anxiously looking forward to the time that I can have one Eclipse installation. I use the MyEclipse plug in for all my Java development and then move over to WDSC when I have RPG or HATS work to do. That is because, as I understand it, the Eclipse platform is at 3.0.2.2 for WDSC and I need 3.1.2 (minimum) for MyEclipse. At Spring Common I was told that WDSC will support Eclipse 3.2 "just weeks" after the release of Eclipse 3.2. Any idea of when that will be? MyEclipse has just released it's support for 3.2 and I'd like to get to one Eclipse install soon.-- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.