so you would rather never support java 11 than releasing a Xtext 3.0
or would you simply bump the dependencies, try to use guava 24-21 api
only and dont care about manifest compatibility?

how does that fit with orbits policy to delete stuff?


Am 03.09.2018 um 08:38 schrieb Sven Efftinge:
> Because of the huge impact with bumping the major version, we never do
> that, even if we can't avoid breaking a couple of clients.
> It is just better to break a hand full of clients than stopping
> everyone from updating to the latest version.
> There is no general answer, it always depends on whether the benefits
> of such an upgrade carry the downsides (breaking).
> Bumping the major version has such bad downsides that I'd consider it
> never being a good idea.
>
> On Mon, 3 Sep 2018 at 08:31, Christian Dietrich
> <[email protected] <mailto:[email protected]>>
> wrote:
>
>     The main problem is:
>
>     what if e.g. java 11 requires to update these libaries?
>     how did you handle that is the past?
>     (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5816)
>     which was done in Nov. 2011 which was likely Xtext 2.1 or 2.2
>     => no major version bump
>
>     => i'am totally unsure what binary compatibility means regardings
>     dependencies / manifests (we have other things that break e.g. through
>     orbit changes
>
>     Thanks
>     Christian
>
>     Am 03.09.18 um 08:22 schrieb Sven Efftinge ([email protected]
>     <mailto:[email protected]>):
>     > Hi Christian,
>     >
>     > those libraries are used by users, so those changes will be
>     exposed to
>     > them. I haven't looked closely into what API has changed in
>     those versions,
>     > but if they have bumped the major version, there might be
>     something in it
>     > that breaks. I assume they follow semantic versioning, too.
>     >
>     > That said, bumping Xtext's major version will be a huge problem
>     for Eclipse
>     > clients, because older existing versions will not work with it. And
>     > because we have singleton plug-ins in every Eclipse installation
>     there can
>     > be only one version of Xtext. We have discussed this for years.
>     Bumping the
>     > major version is a bad idea.
>     >
>     > Sven
>     >
>     >
>     > Am Sa., 1. Sep. 2018 um 14:31 Uhr schrieb Christian Dietrich <
>     > [email protected] <mailto:[email protected]>>:
>     >
>     >> Hello guys.
>     >>
>     >> i need your assistance with regards the rules op api changes
>     and version
>     >> bumps.
>     >>
>     >> if we increase our dependency at Xtext to Guice 4.x and Guava
>     23.x would
>     >> that require a Xtext 3.0? i am not sure if binary compatibility
>     is given
>     >> by such a change.
>     >>
>     >> Thanks
>     >> Christian
>     >> --
>     >> Christian Dietrich (Diplom-Informatiker (BA))
>     >> Softwareentwickler / -Architekt
>     >>
>     >> Tel.: +49 (0) 711 / 34 21 91-0
>     >> Fax.: +49 (0) 711 / 34 21 91-29
>     >> Mobil: +49 (0) 151 / 173969 17
>     >> Mail: [email protected]
>     <mailto:[email protected]>
>     >> XING: https://www.xing.com/profile/Christian_Dietrich8
>     >> Web: http://www.itemis.de
>     >> Skype: christiandietrich1982
>     >> ICQ: 125801794
>     >>
>     >> itemis AG
>     >> Niederlassung Süd
>     >> Industriestraße 6
>     >> 70565 Stuttgart
>     >>
>     >> Rechtlicher Hinweis:
>     >> Registergericht: Amtsgericht Dortmund HRB 20621 | Sitz der
>     Gesellschaft:
>     >> Lünen
>     >> Vorstand: Jens Wagener (Vorsitzender) | Wolfgang Neuhaus
>     >> Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.) | Michael Neuhaus |
>     >> Jennifer Fiorentino
>     >> _______________________________________________
>     >> modeling-pmc mailing list
>     >> [email protected] <mailto:[email protected]>
>     >> To change your delivery options, retrieve your password, or
>     unsubscribe
>     >> from this list, visit
>     >> https://dev.eclipse.org/mailman/listinfo/modeling-pmc
>     >
>     >
>     > _______________________________________________
>     > modeling-pmc mailing list
>     > [email protected] <mailto:[email protected]>
>     > To change your delivery options, retrieve your password, or
>     unsubscribe from this list, visit
>     > https://dev.eclipse.org/mailman/listinfo/modeling-pmc
>     >
>
>     -- 
>     Christian Dietrich (Diplom-Informatiker (BA))
>     Softwareentwickler / -Architekt
>
>     Tel.: +49 (0) 711 / 34 21 91-0
>     Fax.: +49 (0) 711 / 34 21 91-29
>     Mobil: +49 (0) 151 / 173969 17
>     Mail: [email protected]
>     <mailto:[email protected]>
>     XING: https://www.xing.com/profile/Christian_Dietrich8
>     Web: http://www.itemis.de
>     Skype: christiandietrich1982
>     ICQ: 125801794
>
>     itemis AG
>     Niederlassung Süd
>     Industriestraße 6
>     70565 Stuttgart
>
>     Rechtlicher Hinweis:
>     Registergericht: Amtsgericht Dortmund HRB 20621 | Sitz der
>     Gesellschaft:
>     Lünen
>     Vorstand: Jens Wagener (Vorsitzender) | Wolfgang Neuhaus
>     Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.) | Michael Neuhaus |
>     Jennifer Fiorentino
>     _______________________________________________
>     modeling-pmc mailing list
>     [email protected] <mailto:[email protected]>
>     To change your delivery options, retrieve your password, or
>     unsubscribe from this list, visit
>     https://dev.eclipse.org/mailman/listinfo/modeling-pmc
>
>
>
> -- 
> Sven Efftinge
>
> TypeFox GmbH
> Am Germaniahafen 1
> 24143 Kiel
>
> Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385
> Managing Directors: Sven Efftinge, Moritz Eysholdt, Dr. Jan Köhnlein
>
>
> _______________________________________________
> modeling-pmc mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/modeling-pmc

_______________________________________________
modeling-pmc mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/modeling-pmc

Reply via email to