Issue #589 has been updated by Raphaël Ouazana. Status changed from Assigned to Feedback Assigned to changed from Raphaël Ouazana to Clément OUDOT % Done changed from 0 to 70
I've committed a partial fix. Now the task are always taken in the order defined in the configuration, instead of a random order. So if you have defined in your lsc.xml : - task a - task b - task c And then you run : lsc -s c,b,a -c b,a,c The real order is : sync a, clean a, sync b, clean b, sync c, clean c For now no more will be done in this area, because it will prevent cleaning of a task to be done juste after syncing, causing potential regressions for some configurations. ---------------------------------------- Bug #589: Order of tasks is not managed http://tools.lsc-project.org/issues/589 Author: Clément OUDOT Status: Feedback Priority: Normal Assigned to: Clément OUDOT Category: Core Target version: 2.1 Problem in version: If we start LSC with -s task1,task2, task3, the order is not taken into account when launching tasks. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
