On 3/20/07, Maarten Coene <[EMAIL PROTECTED]> wrote:
Hi, we have some libraries which may not used together. For instance, - say we have module A-1.0, A-2.0, B and C. - B doesn't have a dependency on A, but B cannot be used together with A-1.0. However, B can be used together with A-2.0. - C has a dependency on both B and A-1.0 What is the best way to configure Ivy so that it fails when I try to resolve the dependencies of module C? Manual checking this in Ant after a resolve could be an option, but I want to enforce this in IvyDE as well...
The only way I see with current Ivy implementation is to register a custom Trigger on the EndResolveEvent and throw an exception if the resolve report contains both B and A-1.0. Not a beautiful solution, but should work. Otherwise we'd need to introduce a new syntax in Ivy files to declare the incompatibility. Would be nice, but requires work on Ivy. - Xavier regards,
Maarten ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news
