Issue #108 has been updated by Jonathan Clarke.
The reason this doesn't work is that ant launches the task from the target/classes folder. So a relative path is accepted, but must be relative to target/classes, not the current directory. We could just drop support for target/classes as soon as the configuration directory is fully functional. In fact, most old installations will still work, because they won't update their build.xml file from the sample. What do you think? ---------------------------------------- Bug #108: Cannot change configuration directory http://tools.lsc-project.org/issues/show/108 Author: Cl?ment Oudot Status: Feedback Priority: Normal Assigned to: Jonathan Clarke Category: Core Target version: 1.1.0 I try to use an alternate configuration directory with this command: <pre> ant -Dsynchronize.parameters="-s all -c all -f src/test/resources-test/" lsc::synchronize </pre> This does not seems to work. -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20090720/b5c52b4d/attachment.htm>
