Quick reply. It is possible to associate a particular organisation or module with a particular resolver, but it's a really advanced bit of configuration, and I don't recall offhand what it is. I remember having to do this once myself, but it was for a certain module or org for which I had no choice (possibly because the public repo wasn't giving me what I wanted--don't recall exactly why).
For what you're describing, trusting the chain resolver is the established way to go. Trusting chain resolvers in general is the established way to go, since even if you get rid of all public repositories and bring all third-party dependencies in-house, you're still going to gravitate toward chains of repositories in all but the simplest situations. Besides, the more third-party dependencies you get from public repositories, the uglier your Ivy settings is going to get. It will end up looking like one big ivy.xml file with the dependencies themselves, and that's not what you want. Ivy dependencies and Ivy configuration are best thought of as two orthogonal things. On Mon, Mar 5, 2012 at 7:40 AM, Jasper Floor <jasper.fl...@m4n.nl> wrote: > Hi, > > While I'm sure someone must've had my question in the past I cannot > find any (satisfactory) answer. > > Basically I have a project in which the dependencies may come from > different locations. Eventually everything will be handled by a > private internal repository but for now I'm still using public ones. > Also, I would like to be able to define them anyway just in case the > internal repository gets blown up by terrorist mice taking revenge for > their fallen comrades. > > To simplify, lets say I have two depencies, A and B. A can be found on > the regular ibiblio repository while B can only be found on the Jboss > Repository. > So I need A to resolve from ibiblio and B to resolve from the jboss nexus. > > I could do this with a chained resolver except this feels messy to me. > I know that A will never resolve from jboss and I know that B will > never resolve from ibiblio. Is there anyway to link a dependency to a > specific resolver? Or will it always have to go through a chain? > > thanks in advance. > > mvg, > Jasper >
