Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [qvtd-dev] QVTd progress to M1
Hi

Today the tests are the only way, although it's only Java code, so you can write your own launcher.

In due course we will want a proper Eclipse launcher. This will probably come 'for-free' when doing the debugger and/or builder.

We could also provide an Ant task and MWE workflow component.

Any other ideas?

    Regards

        Ed


On 19/08/2013 10:50, Horacio Hoyos Rodriguez wrote:
Hi Ed,

The CG code looks nice. Is running the tests the only way of running the CG code? 

I have rebased the previous branch I had on master. Will do the same with the current one to move the etl plugin to the master branch. 


On 19 August 2013 10:01, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
Hi Horacio

GIT master is now as I plan it fior M1. The CSE for CG is in place and uml2rsdbms.java is compilation error free. You might want to see how well it runs and create reference test data.

I'm currently working on saving  and loading pivot models. This involves API evolution too close to M1, so will probably happen late in the week, after M1 is frozen.

You might therefore want to update to OCL master and rebase your branches on QVTd master. (Rebase makes for a much tidier long term GIT history.)

You might also want to delete some of your old branches. (There is a Push Delete option in the GIT Push dialog.) If you want a long term record of a particular successful state, create a Tag rather than leave an old branch around. If you want a long term record of a particular unsuccessful state, rename the branch to archive/....

    Regards

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



--
Horacio Hoyos Rodríguez
EngD Student
University of York 



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


No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3392 / Virus Database: 3211/6588 - Release Date: 08/18/13


Back to the top