|Re: [tycho-dev] Tycho to require Java 11|
As you have mentioned this will affect (and break!) existing builds, so
it is not only "upgrade the build jvm", so I'm not very convinced to
move to java 11 without any additional benefit, these backward
incompatibilities since java 7 release are IMO one of the worst decisions.
So what are the real benefits of moving to java 11? Can we dramatically
Can we support features currently not
possible and long demanded by the community? Are there any major
libraries (maven?) that force us because we can't upgrade any more?
If none of the above applies I fear people will be more frustrated than
feeling helpful by forcing them to use java 11 and instead will stick at
older tycho releases.
At least we should then move to Tycho 2.0 version to clearly state the
Am 26.03.20 um 18:11 schrieb Aleksandar Kurtakov:
> In the light of Eclipse Platform moving to require Java 11 as a minimum
> in September  I think we should move Tycho prior to that.
> Reasons are:
> 1. It will affect only JVM version runtime at build time. One can freely
> target older JVMs as it's done in e.g. Eclipse Platform release where
> build is running on Java 11 but there are bundles targeting down to Java 1.3
> 2. It will help a number of projects to ensure that additional bundles
> are in project's target platform and p2 repositories for APIs removed in
> newer Java versions (xml.*, inject, annotation....)
> 3. Projects will update their CIs JVMs
> 4. Message about ecosystem move to Java 11 will get more attention and
> less people will be surprised in September.
>  https://www.eclipse.org/lists/cross-project-issues-dev/msg17532.html
> Alexander Kurtakov
> Red Hat Eclipse Team
> tycho-dev mailing list
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-dev
tycho-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-dev
Back to the top