[Jeremy Kuhnash]

Shouldn’t updating myEclipse from the plugin update system be a high priority for myEclipse integration?

What can I say … myEclipse is ideal for all my needs and every time I think of a feature, it is in the newest release. Which I install every 2-3 weeks or so .. from scratch and then manually re-install all my other plugins.

I saw that a manual install version of myEclipse exists, but considering the architecture of Eclipse is being leveraged by the rest of the myEclipse project, why isn’t the plugin update system? If there is something lacking within the core Eclipse framework, wouldn’t fixing that be a fairly high priority? The only thing I can think of is authentication of the update to be a valid subscribed user …

Thanks for the great product.

— Jeremy

[Riyad Kalla]

Jeremy,
First let me thank you for the support, 2nd the Update system currently has limitations that we have to work around. For example between Beta 2 and 3.8.0 and then again in 3.8.1 we removed/refactored some plugins. The Eclipse Update mechanism is only additive meaning we can’t erase or remove deprecated plugins. I think one of the biggest reasons you don’t see this with other plugins is that these other plugins are 1, 2 or maybe 3 plugins… MyEclipse consists of ~130 separate plugins so the chance of 1 getting deprecated or renamed is about 100x better than it happening in one of the other smaller single-plugin projects.

We hope after the major changes in 3.8.0 start to stabalize that this *jumping around* that requires full installs will stop.

[Jeremy Kuhnash]

Awesome to hear. Additionally, I do understand that working on myEclipse and Eclipse core to enhance the plugin architecture is too much to ask. I am not plugged in enough to know but open source works best when you give a project code and say ‘here just patch this in..’ 😉

Good work and I hope to see this sometime in the future.

[Author]

Posts