Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [qvtd-dev] Project synchronization
Hi Horacio

You are using

OCL: [387973] Fix and test Pivot with standalone classpath]


which is on branch edw/387973 which is a bug fix for maintenance/R4_0 so you have actually gone backwards to M0'; not surprising that this is confusing. (Browse the GIT history view and you'll see what's happening.)

You should be using M4, which is tagged:

commit 44cfb947de8eed9acfb069ebf842962dd8cc9997
Author: Ed.Willink <ed@xxxxxxxxxxxxx> 2012-12-18 22:58:42
Committer: Ed.Willink <ed@xxxxxxxxxxxxx> 2012-12-19 14:08:32
Branches: M4, edw/389120a, edw/389120b, edw/M4, master, origin/edw/389120, origin/master
Tags: Kepler_M4_Tools

[releng] Missing about.html's

commit 9bbce0da2b3cf44d9938dc7c5916dd6ca9a6ed1c
Author: Ed.Willink <ed@xxxxxxxxxxxxx> 2012-12-19 19:59:06
Committer: Ed.Willink <ed@xxxxxxxxxxxxx> 2012-12-19 19:59:06
Parent: 196d9a801a1478fd381cfd134ec845987903c7f7 ([unrelated] Track additional OCL API)
Child: 7f8b45a82dc39ce5c53564ded8369e56e751742a ([ocl] Track OCL API change avoiding ScopeFilter leaks)
Branches: M4, master, origin/master
Tags: Kepler_M4

[releng] Update repos

So you are miles off on the OCL and two commits off on QVTd.

Options:

a) use M4 as recommended. - need to back up qvtMustus to QVT M4.
b) advance OCL 2 commits, since the two commits were committed (locally) on 20-Dec, but not pushed till much later so there is no obvious OCL counterpart, so moving on two commits is not an option.
c) advance OCL and QVTd to latest commit on master
d) abort and wait till M5 to synchronize

Unhelpfully qvtMustus has no tags, so you might like to browse the Eclipse repos directly to see them.

    Regards

        Ed




On 24/01/2013 17:22, Horacio Hoyos Rodriguez wrote:

Hi Ed,

 

Have you checkout M4 of both OCL and QVTd?

 

I am getting OCL from git and have used http://download.eclipse.org/releases/kepler to update my eclipse to M4

 

Have you refreshed and built your workspace?

 

Yes

 

What commit/tag of OCL, QVTd, QVTmustus are you using?

 

OCL: [387973] Fix and test Pivot with standalone classpath]

QVTmustus: 9fe89f4 (and updated from QVTd through fetch and merge from upstream)

 

 

What errors do you get?

 

In the patch you sent me you removed the creation of ObjectValue (QVTcoreEvaluationVisitorImpl visitPropertyAssigment) since the initValue received an Object instead of an ObjectValue. However the DomainProperty interface (commit b479800 – 4 days ago) it expects an ObjectValue again.  This is the patch:

 

if (slotBinding != null) {

-                    ObjectValue ov = ValuesUtil.createObjectValue(slotBinding);

+//                    ObjectValue ov = ValuesUtil.createObjectValue(slotBinding);

                     Property p = propertyAssignment.getTargetProperty();

-                    p.initValue(metaModelManager, ov, value);

+                    p.initValue(slotBinding, value);

                 }

 

Similar happens in the Type. createInstance() changes. My current version seems to still be expecting the “old” version. Either I am downloading something wrong or you reverted to the version I used.

 

Regards,

 

Horacio Hoyos Rodríguez

EngD Student

University of York

 

 

-----Original Message-----
From: qvtd-dev-bounces@xxxxxxxxxxx [mailto:qvtd-dev-bounces@xxxxxxxxxxx] On Behalf Of Ed Willink
Sent: 24 January 2013 16:59
To: QVTD developers mailing list
Subject: Re: [qvtd-dev] Project synchronization

 

Hi

 

Have you checkout M4 of both OCL and QVTd? Have you refreshed and built your workspace?

 

What commit/tag of OCL, QVTd, QVTmustus are you using?

 

What errors do you get?

 

     Regards

 

         Ed

 

On 24/01/2013 15:26, Horacio Hoyos Rodriguez wrote:

> Hi Ed,

> 

> I applied your patch but got errors from Type.createInstance(),

> Property.initValue() methods. I have fetched the latest OCL changes so

> now

> 

> I am lost as what is the correct method declaration.

> 

> 

> Regards,

> 

> Horacio Hoyos Rodríguez

> EngD Student

> University of York

> 

> 

> -----Original Message-----

> From: qvtd-dev-bounces@xxxxxxxxxxx

> [mailto:qvtd-dev-bounces@xxxxxxxxxxx]

> On Behalf Of Ed Willink

> Sent: 20 January 2013 11:50

> To: QVTD developers mailing list

> Subject: Re: [qvtd-dev] Project synchronization

> 

> Hi Horacio

> 

> On 20/01/2013 10:36, Ed Willink wrote:

>> The problem is that I have evolved the mutation 'API' to support code

>> generated execution:

>> That is: Type.createInstance(), Property.initValue() have changed.

>> 

>> For these particular methods I should have provided delegating

>> methods and deprecation. Will rectify for M5.

> I developed the delegations but then realized that actually you

> started using the M2 API after M4, so they are unnecessary.

> 

> Attached patch fixes the build problems, adapts to the API changes and

> provides a launch config so that there are three green tests for your

> code

> 

> built against OCL M4 and QVTd M4.

> 

>       Regards

> 

>           Ed

> _______________________________________________

> qvtd-dev mailing list

> qvtd-dev@xxxxxxxxxxx

> http://dev.eclipse.org/mailman/listinfo/qvtd-dev

> 

> 

> -----

> No virus found in this message.

> Checked by AVG - www.avg.com

> Version: 2013.0.2890 / Virus Database: 2639/6052 - Release Date:

> 01/23/13

> 

> 

> 

 

_______________________________________________

qvtd-dev mailing list

qvtd-dev@xxxxxxxxxxx

http://dev.eclipse.org/mailman/listinfo/qvtd-dev



_______________________________________________
qvtd-dev mailing list
qvtd-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/qvtd-dev


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


Back to the top