For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 2 voices, and was last updated 21 years, 1 month ago by
.
-
Posts
-
I’m a bit curious about why MyEclipse developers chose to re-version some 3rd party applications, as it is ending up causing some hassles trying to keep current with those plugins…
Specifically, the SpringIDE plugins are officially in the 1.2.x series, yet presumably the same plugin (it has the same package/plugin name) in MyEclipse4.0M2 is versioned 3.9.210/211. Then the MyEclipse Spring feature references these new version numbers…
It seems a little curious why MyEclipse would re-version a project like this, making it difficult for a user to know what version of the 3rd party plugin they are using (and therefore what bugs/features it has).
Wouldn’t it be simpler just to use the 3rd-party plugin version numbers, and have the MyEclipse feature reference those versions? So if a user wanted to upgrade to the new 3rd-party plugin they could do so without having to modify their MyEclipse install?
It would be nice if MyEclipse would provide an easy way to keep current with some of the 3rd party plugins, so users dont have to wait for MyEclipse developers to get around to updating them. (I’m sure they have more important things to do than try to keep up-to-date with every release of every 3rd party plugin!)
Thanks.
Troy
Troy,
Each and every plugin we integrate is hooked into the MyEclipse framework at different levels. We don’t ship a single plugin that is simply a “drop in” install. Because of this there is no simple “drop in upgrade” available for these plugins. If you were to drop SpringIDE into MyEclipse, while most of it might work, there are likely other functionalities that would totally break. We need to keep good control over what versions of what plugins are installed with MYEclipse, that is why we currently do things this way.I can understand that, it sounds rational enough.
At any point, will myeclipse be offering an update site for 4.0 that will be able to update selected 3rd party plugins as new versions of those plugins become available? (for example, the SpringIDE components which have added some rather significant features since the release of MyEclipse 4.0M2) And would MyEclipse consider exposing the true version information about the 3rd party plugins so that users can make informed decisions regarding their development environment?
(P.S. I find a great deal of value in the MyEclipse offering, I think it is a great help for myself, and my development team. However, it’s a little hard to accept being constrained by the versions of plugins that MyEclipse releases. It would be nice to have either/both the version information for those plugins, and/or a way up updating selected/all plugins in a release as new version are released/tested.)
We are painfully aware of our growing need for something like this and have actually been planning individual-module-based-updates since 3.9, it’s just been an issue of having a good time to roll it out.
Something to this effect (upgrading the parts of MyEclipse you use) will rollout soon, not sure exactly but originally it was planned to come out around 4, so either then or soon there after.
