| Re: [qvtd-dev] Project synchronization |
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-----
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 > 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 |