- This topic has 2 replies, 3 voices, and was last updated 15 years, 6 months ago by
.
-
Posts
-
Dear all,
I would like to hear your opinion about MyEclipse and incompatibilities to “standard” eclipse projects like DTP and WTP.
For me, these incompatibilities get more and more problematic and it seems, that there is no focus in the myeclipse team to achieve more compatibility.
For example: I need to work with one or two plugins wich need DTP database connection definitions. No way, I have to use a separate eclipse installation.
Next example: Some plugins rely on the WTP server definitions. I don’t have them in MyEclipse and as far as I know, they would interfere with MyEclipse if I tried to get them running. I can remember the history of myeclipse – they had a server integration and database connection long before DTP and WTP were ready to be used.
But this history is very long ago. Citing the sticky topic “What is WTP” in this forum: “Our response is simple. WTP is one of many sources for features MyEclipse will continue to integrate into the Enterprise Workbench in our continued effort to provide the most comprehensive J2EE IDE on the market.” This topic is from 2003/2004! I can still only run one (integrated) tomcat of one version while WTP does a better job.
The “Blue edition” is praised as “anti lockin IDE” (I don’t really know the blue edition), should it better be called “lockin to us instead of IBM Edition”?
In case I just simply miss something: Is there a way to get WTP and DTP running inside the same installation while still having MyEclipse fetaures?
Did somebody already consider switching “back” to the “standard” Eclipse distributions, like I start to consider sometimes?
Best regardsFor me, these incompatibilities get more and more problematic and it seems, that there is no focus in the myeclipse team to achieve more compatibility.
There is actually, work has already begun in this realm (for WTP project compatibility) and was shipping in MyEclipse Blue 7.1 — we are doing the work incrementally and very carefully. After all, if you break a project, you break everything. We started with more well-known and controlled environments and have been rolling out code changes slowly to increase the support.
I imagine we’ll have fully transparent WTP project support (e.g., just opens and works fine without any messing around) in the 8.x release series. Possibly sooner, but I don’t want to promise and than not be able to deliver it.
For example: I need to work with one or two plugins wich need DTP database connection definitions. No way, I have to use a separate eclipse installation.
Rectifying inter-operability with DTP isn’t really on an immediate roadmap right now, sorry about the inconvenience.
>>Did somebody already consider switching “back” to the “standard” Eclipse distributions, like I start to consider sometimes?
Yes. All new development at my shop is happening under standard Eclipse WTP. MyEclipse 7.1 is horribly slow, and the bugs and poor documentation is costing me more time than it is worth just to get going. We only renewed a third of our subscriptions and plan to migrate legacy projects completely out of MyEclipse.
The startup time, hangs and general bloated feel of MyEclipse 7 is just unacceptable compared to standard WTP Ganymede.
A simple thing, such as editing web.xml by highlighting a section of code with keyboard only (not mouse) wil fail to update for several seconds until the IDE “catches up”. And that is with all validators turned off on a Core 2 Duo Extreme with 4GB RAM.
