Hi, the VIATRA project is not ready to move to Guava 21, as we still use Java 7 as a minimum requirement, while Guava 21 requires Java 8. We are now in the process of figuring out whether we can set up dependency ranges and uses constraints in a way that we can work both with Guava 15 and 21 (even if both are installed); if everything works as we expect, we will not block moving Oxygen to Guava-only.
If we do not explicitly require Guava 21, but support it through version ranges, do we have to fill a corresponding PB CQ? Best regards, Zoltán -- Zoltán Ujhelyi Eclipse Technologies Expert IncQueryLabs Ltd. > On 2017. May 5., at 10:04, Aleksandar Kurtakov <[email protected]> wrote: > > On the last Planning council meeting we discussed Guava and having > multiple versions of it in Oxygen. In order to prevent issues like > there were with multiple Guava versions in Luna and/or issues like > with Neon.3 we are strongly recommending that: > > Every project that depends on Guava moves to version 21 for Oxygen. > > > Guava 21 is available in Oxygen's M6 repo so please file your PB CQs > and move up ASAP. > Detailed report of all the API changes since version 15 (the version > in Neon) can be found at > https://github.com/google/guava/wiki/ReleaseHistory . > > Don't hesitate to ask if there is anything unclear. > > -- > Alexander Kurtakov > Red Hat Eclipse Team > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
