Re: [ide-dev] A "releases/latest" URL in the IDE to ease upgrades?
I'm also for the IDE leading innovation to the users,
But I think users might be dependent on platform version, then
switching could break APIs and cause migration issues
As an user:
- when I click on "check for updates", I expect
"simple"(in-the-same-major-version) plug-ins updates, and not major
- I might be dependent on a specific platform version.
a. the Eclipse IDE can detect a major release update.
b. the Eclipse IDE can handle the platform update
During a "check for updates", if a major update is available, a
possible workflow could be:
1. Ask the user: "A new major update is available. Auto-update the platform?"
2. Show a message "Updating to the latest version:" + drop-down
(select available higher versions)
Note: I'm dependent on platform version, as I develop plugins on
Kepler (4.3), and I will have migration issues (...) in switching to
On Thu, Dec 3, 2015 at 5:34 PM, Mickael Istria <mistria@xxxxxxxxxx> wrote:
> On 12/03/2015 05:29 PM, Max Rydahl Andersen wrote:
> Your expectation about good management of dependency versions we know from
> JBoss Tools and our attempt to get a build running for Eclipse next release
> just never works.It does for the base platform, but very rarely beyond that.
> At some point, I believe the IDE has to "lead" the ecosystem, by being more
> helpful to its users, including allowing updating from Mars to Neon, and
> that 3rd-party in the ecosystem have to adapt accordingly or die. Eclipse
> IDE doesn't have to handle all the pain created by 3rd party plugins and
> should be really focusing on its users more than on all the possible ways
> for 3rd-party plugins to mess it up.
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
> ide-dev mailing list
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit