On 8/15/07, Jeffrey Blattman <[EMAIL PROTECTED]> wrote: > > i don't mean to rain on dmitry's great explanation, but i think this > might be the crux of the problem. there is one way to do it on maven, > and no one has any questions about it. i to was / am confused by > configurations in Ivy.
Not sure to get what you are meaning. Do you mean that we should only provide one way to specify configuration mapping, or that we should simply not provide flexible configuration mapping as we do? Maven has no concept of configuration, they have scopes which are predefined and do not allow things as flexible as you can do with Ivy. But maybe providing an easy to use configuration mapping in Ivy could help users who don't want to take care about understanding the real flexibility of configurations. Xavier Dmitriy Korobskiy wrote: > > > > 2. How to specify this mapping? There are many ways in Ivy to do it. > Let's start > > with explicit abbreviated mapping for each dependency: > > > > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
