Hi
I've chosen to do QVTo first since it's probably easiest. (Maybe
but custom Ant tasks are always painful.)
For the most part Tycho is much nicer than Buckminster. It
actually succeeds in providing something that executes in your
normal workspace. (Just install m2e from SimRel, update your
workspace and run the m2e->Build QVTo launch.) I have packaging
and tests working but strangely the source plugins are omitted.
The tests use the packaged results rather than the build workspace
so they are a better test, but they are two JVM invocations away
from a debugger.
Now I have to sort out signing and promoting, which can only be
done on a master build. I'll therefore be making use of a new
qvto-photon-master job.
I'll bump all feature versions to 3.8.0. Only one cosmetic plugin
signature no-change was need to fix an error while I accidentally
used Java 1.8.
Do not trust any 3.8.0 promotions until I'm done.
Regards
Ed Willink
On 25/08/2017 10:18, Sergey Boyko
wrote:
Hi Ed,
Yes, you're right. Seems that moving to Tycho is the only
option for our build infrastructure. Hope this can guarantee
stable releases for next few years until next "new technology"
will appear :)
Certainly the main difficulties is to move OCL to Tycho.
Once it's done then duplicating it for QVT* projects won't be
so complicated.
Of course I'll be very grateful if you will try to move
QVTo to Tycho. Or once OCL will be bready I can try to
"copy-paste" the solution myself.
Best Regards,
Sergey.