|How to enforce ordering of Oomph steps? [message #1724864]
||Fri, 26 February 2016 15:51
| Zoltan Ujhelyi
Registered: July 2015
we are in the process of setting up an Oomph-based setup for the VIATRA project. One of our challenges is that we do not upload generated code to version control, so we have to execute some code generation steps before the developer can begin to work.
For this reason, we are executing some Launch configurations that execute code generation. However, these configurations depend on the target platform to be set up correctly, in other words, we have to execute the Targlet step before these Launch configuration steps.
On some computers this happens as expected, while on others, Targlet setup is executed consistently after the launch configuration. We have tried to put Targlet setup before the launch step; and also tried to add Predecessors/Successors references using the Advanced Properties, however it does not seem to be working (both the predecessors attribute of the launch configuration is set to include the targlet task; both the successors attribute of the targlet is set to include the launch configuration).
Are we missing something here? Is there any way to consistently enforce an ordering between these steps?
Thank you for the help,
Powered by FUDForum
. Page generated in 0.01626 seconds