Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

t; > Thanks, > > > > - Konstantin > > > > > > > From: cross-project-issues-dev-boun...@eclipse.org > [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Sebastian > Zarnekow > Sent: Monday, September 14, 2015 6:24 AM > To: Cros

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

project-issues-dev@eclipse.org>> Date: Tuesday, September 15, 2015 at 8:57 AM To: Cross project issues <cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>> Subject: Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences Hi,

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

on being coupled with semver of plugins which >> doesn't make much sense to me. If there is API breaking change in a bundle >> it doesn't mean that this justifies bumping Eclipse (platform) version. >> What about bringing it to next Architecture council for faster discussion >>

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

eclipse.org <mailto:cross-project-issues-dev-boun...@eclipse.org>] *On Behalf Of *John Arthorne *Sent:* Monday, September 14, 2015 7:27 AM *To:* cross-project-issues-dev@eclipse.org <mailto:cross-project-issues-dev@eclipse.org> *Subject:* Re: [cross-project-issues-dev

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

stantin Komissarchik" <konstantin.komissarc...@oracle.com> > > To: "Cross project issues" <cross-project-issues-dev@eclipse.org> > > Sent: Monday, 14 September, 2015 5:25:46 PM > > Subject: Re: [cross-project-issues-dev] Unannounced Changes Have > Unforeseen

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

Indeed, breaking API without major version changes is an absolute no go. Even if only a few percent of existing plugins are affected, this undermines the idea of APIs and semantic versioning. see also https://wiki.eclipse.org/Evolving_Java-based_APIs

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of John Arthorne Sent: Monday, September 14, 2015 7:27 AM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences Hi

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

Hi, I totally second Eds and Eds remarks here. All API policies and all the bundle versioning schemes and careful changes in the past would be rendered pointless with this move. I doubt that keeping the deprecated interfaces is causing effort for the maintainers that is coming even remotely close

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

ect-issues-dev@eclipse.org > *Subject:* Re: [cross-project-issues-dev] Unannounced Changes Have > Unforeseen Consequences > > > > Hi everyone, > > > > This has been a great discussion. I have a few points to add: > > > > - It is very important for the P

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences Hi everyone, This has been a great discussion. I have a few points to add: - It is very important for the Platform (and other projects) to have the right to occas

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

org>] *On Behalf Of *John Arthorne *Sent:* Monday, September 14, 2015 7:27 AM *To:* cross-project-issues-dev@eclipse.org <mailto:cross-project-issues-dev@eclipse.org> *Subject:* Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences H

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

Ian, That's exactly the key issue that concerns me most. In general I've felt uncomfortable with the version ranges for two reasons. Firstly because I believe that once set, the lower bound is likely never carefully reconsidered as to whether it remains valid. As such, I'm willing to bet

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

Hi Ed W. https://bugs.eclipse.org/bugs/show_bug.cgi?id=475944 is about marking the API for deletion, this would follow the normal process, of marking, waiting two releases and afterwards (potentially) delete it. There was a suggestion to delete it in this release, but that is no going to happen

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

The reason it was not considered an API breaking change was explained to me in [1]. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=475833#c15 Cheers, Ian On Sat, Sep 12, 2015 at 10:05 AM, Doug Schaefer wrote: > This affected CDT too. Luckily we were some what prepared

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

This affected CDT too. Luckily we were some what prepared and had one or our crack committers fix it but it did force us to make a change to continue on with Neon. So, I¹m not sure how this is not an API breaking change, deprecated or not. I believe the Platform is going to have to ask the

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

Hi TableTreeViewer removal was announced in http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fporting%2Fremovals.html But IPlatformRunnable is only announced as after June 2017 in