[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [qvtd-dev] Project synchronization
|
Hi Horacio
It would be much simpler to stick as major releases, but there will
inevitably be enhancements to the models and editors, so 6-weekly
milestones is a plausible compromise.
It's probably easiest to just update from
http://download.eclipse.org/releases/staging a few days after the
milestone release. This should pick up everything.
Other dependencies such as EMF, UML2 and Xtext are less likely to change
so you may get away with changing them much less often.
Regards
Ed
On 21/01/2013 17:22, Horacio Hoyos Rodriguez wrote:
Hi Ed,
Should the QVTd development be carried out on a pre-release version of
eclipse (Mx)? If so, does it also have to use latest builds from required
dependencies?
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/6045 - Release Date: 01/20/13
