Re: [mdt-ocl.dev] Probable move to Java 7 classes for Eclipse OCL in Mar

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi Sergey

The move to 7 is underway.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=464193

Unfortunately 4 declarations fail under Java 7 that were ok under Java 5 / 6. It looks like we can keep binary compatibility and have only minor source compatibility issues. See the bug.

    Regards

        Ed Willink

On 02/04/2015 17:40, Sergey Boyko wrote:

Hi Ed,

I also inclined to move to Java 7 for QVTo plug-ins.  And I see no reasons to ask OCL not to move to Java 7.

Regards,

  Sergey.

On Thu, Apr 2, 2015 at 9:59 AM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:

Hi

Some of the Eclipse platform plugins moved to Java 7 classes for Mars M6 and this is causing problems continuing to provide Java 5 (Classic Eclipse OCL) or Java 6 (Pivot Eclipse OCL) plugins. See [1].

The simple solution is to just shift all Eclipse OCL plugins to Java 7 classes.

An alternative is to omit the 'tampered' *.pack.gz files for Mars, and re-introduce them after Mars when the Eclipse OCL build may move to Tycho from Buckminster.

Does anyone have a use case for not moving to Java 7 and so removing all support for Java 5 and Java 6?

(And while I'm asking, does anyone have a problem moving to Java 8 for Mars+1?)

    Regards

        Ed Willink

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=463131
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev

_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5863 / Virus Database: 4321/9435 - Release Date: 04/02/15