Improve workflow run configuration (ModelRunner.txt)
Closed this issue · 3 comments
GoogleCodeExporter commented
Erwin wrote in an email sent today:
With a trial by Andy for the Passerelle vanilla workbench on Linux 64 bit, I
discovered another fragility with that ModelRunner.txt approach.
When building for the different destination platforms (win32, win64,
linux32&64, mac etc), this launch configuration must also be specialized per
target platform to ensure that the right platform-specific fragments of swt,
filesystem etc.
With the move to automated builds on Hudson, Tycho etc at our place, this step
is apparently not working right now. SO I will prepare manual rcp product
builds again for now.
But I was wondering how you handle this in DAWN. Is Buckminster or some other
thing in your tool chain doing this automatically?
Or do you only deliver for one platform?
Anyway, the conclusion for me is that this ModerlRunner.txt thing is something
we have to look at, to make it more flexible.
Both for layering (vanilla vs DAWN) and for target platforms...
Original issue reported on code.google.com by s.olof.svensson@gmail.com
on 13 Mar 2013 at 4:05
GoogleCodeExporter commented
With the agreement of Erwin I'll commit new versions of ModelRunner.txt and
ModelRunner.launch which enables the latest version of Passerelle to be used in
DAWN.
Original comment by s.olof.svensson@gmail.com
on 13 Mar 2013 at 4:07
GoogleCodeExporter commented
I have committed the new workflow run configurations:
https://code.google.com/a/eclipselabs.org/p/passerelle/source/detail?r=1370
Original comment by s.olof.svensson@gmail.com
on 13 Mar 2013 at 4:21
GoogleCodeExporter commented
I have created some platform-specific fragments for the ModelRunner.txt thing,
for macosx, linux 32&64 bit, windows 32&64 bit.
So the ModelRunner.tx is no longer in the
com.isencia.passerelle.workbench.model.editor.ui bundle, but dedicated
ModelRunner.txt files are in the separate fragments.
The product build includes these fragments and is then able to use the right
fragment per target system platform.
I have tried the win 32 & 64 bit versions already. Before I had the same error
as Andy saw. THis is resolved now.
I propose that you also create one or more fragments for DAWN's ModelRunners,
and refer to these in your product builds.
In this way, we resolved both issues : platform-specific stuff and layering of
DAWN vs Passerelle vanilla.
Original comment by erwin...@gmail.com
on 19 Mar 2013 at 9:13
- Changed state: Fixed