Re: [qvto-dev] Compilation error

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

Correct: org.eclipse.m2m.qvt.oml.ecore.qvtoperational is not in qvto.psf.

Borland never fully migrated to the 'official' OMG models. The imperativeocl seems to be used but not the qvtoperational, (which depends on qvtd).

There may be a trivial project settings fix, but I doubt anyone will ever use it, so why bother?

    Regards

        Ed

On 11/01/2013 11:32, Adolfo Sanchez-Barbudo Herrera wrote:

Easy to check.... and it's not the case... It must be a project outside of your PSF ;)

I think this is the official ecore MM for the language, which is not being used by QVTo code since they use their custom metamodel.

I guess that with the new pivot MM, this plugin won't be used anymore, hence, no need to update/maintain, right ?

Cheers,

Adolfo.

On 11 January 2013 11:08, Ed Willink <ed@xxxxxxxxxxxxx> wrote:

Hi

Shouldn't be a 1.7 thing. All projects should have project specific preferences enforcing 1.5.

More likely you just need to clean/build/refresh a few times.

    Regards

        Ed

On 11/01/2013 11:01, Adolfo Sanchez-Barbudo Herrera wrote:

Hi Ed,

I've found a compilation error which I've not seen before:

Type Name clash: The method getInstance(TypedElement<EClassifier>) of type QVTOperationalToStringVisitor has the same erasure as getInstance(TypedElement<C>) of type ToStringVisitor<C,O,P,EL,PM,S,COA,SSA,CT> but does not hide it

QVTOperationalToStringVisitor.java

/org.eclipse.m2m.qvt.oml.ecore.qvtoperational/src/org/eclipse/m2m/qvt/oml/ecore/QVTOperational/util

line 47

I have some of them, although after changing the compiler compliance level to Java 1.5 I finally got QVTo with free compiler-errors state. It must be a Java 1.7 compiler matter.

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2890 / Virus Database: 2637/6024 - Release Date: 01/10/13

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2890 / Virus Database: 2637/6024 - Release Date: 01/10/13