eclipse-modisco / org.eclipse.modisco

Eclipse Public License 2.0
0 stars 0 forks source link

Maintain Java currency #1041

Closed eclipse-modisco-bot closed 3 days ago

eclipse-modisco-bot commented 3 days ago

| --- | --- | | Bugzilla Link | 553277 | | Status | RESOLVED FIXED | | Importance | P3 normal | | Reported | Nov 20, 2019 10:35 EDT | | Modified | Nov 25, 2019 08:32 EDT | | Blocks | 552989 | | Reporter | Ed Willink |

Description

Some platform plugins such as org.eclipse.core.jobs which is a mandatory dependency of org.eclipse.core.runtime have moved to Java 8 which probably explains why many of the J2SE-1.5 expectations of most of MoDisco result in about 25% test failures.

MoDisco has survived much longer than expected because the build used Helios!

As an Eclipse UI tool, Modisco must track the Eclipse platform and so must move to Java 8 BREE. If there was a sub-MoDisco that operated standalone in the same way as the sub-OCL, sub-UML2, sub-QVT etc projects there might be a case for retaining a Java 5 MoDisco, but with no standalone tests it seems there is no standalone sub-MoDisco.

A few EMF plugins such as KDM, SMM could remain at Java 5, but who cares? Last time I tried to find anyone with a pre-Java 8 use case, the only demand was just 'inertia' / 'tradition'.

eclipse-modisco-bot commented 3 days ago

By Ed Willink on Nov 21, 2019 04:08

(In reply to Ed Willink from comment #0)

which probably explains why many of the J2SE-1.5 expectations of most of MoDisco result in about 25% test failures.

No. Changing to Java 8 seems to make zero difference. Bug 552989 describes the ongoing search for the test failure causes.

eclipse-modisco-bot commented 3 days ago

By Ed Willink on Nov 22, 2019 07:10

(In reply to Ed Willink from comment #1)

No. Changing to Java 8 seems to make zero difference.

Indeed and modisco-dev correspondence provides no use case for Java 5/6/7.

We could revert, but we will just trigger the new 2019-12 diagnostic for advertising a lower BREE than a dependency.

The metamodels could in principle stay at Java 5, but as-is SMM has a hard dependency on org.eclipse.core.runtime so cannot be Java 5, whereas KDM goes via EMF and so only has an optional dependency; could be Java 5.

Not worth the effort, Java 8 all round already done.

eclipse-modisco-bot commented 3 days ago

By Ed Willink on Nov 25, 2019 08:32

Java 8 usage pushed to master for 2019-12M3.