Hi
The recent "Errors when running 2018-12 RC2 on Java 11" thread is just
one of many 'new'-Java problems.
The instability of Java is clearly a major PITA, so that each of Java 8,
9, 10, 11 has resulted in significant breakages that have gradually been
ameliorated.
As a user I see Eclipse as a nice platform that has for many years
hidden the Windows/Linux/MacOS eccentricities. Less obviously, the
platform now nodes to hide the Java 7/8/9/10/11 eccentricities, so that
for the most part an Eclipse application just works. We should not
depend on each project rebuilding with latest-Java workarounds.
Currently each new Java eccentricity seems to be accommodated by dubious
workarounds that do not hide the problem from the user. e.g. I now have
to import javax.annotation into each of my test plugins.
It seems that we need to offer two options.
a) a default Eclipse that maximally hides the Java eccentricities to
give a good user experience. This may require a 're-modularizer' to
counteract Java's incessant migrations.
b) -strict Eclipse for those who want to be precisely in tune with a
Java eccentricity.
Regards
Ed Willink
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
