Colin Sampaleanu wrote: > One way I can think of handling this is to have multiple local repos. A > different repo would be used for each instance of the superproject. I > would still want a backup local repo where other common jars are found, > and I believe I can do this by stacking repos.
This sounds like the right solution. You should have three repositories configured in the following order: 1) local systemwide repo (a local cache for jars. jar that are missing here would be loaded from 2 and stored into 3, so you'd want to refresh this repo every time you change external dependencies of your project) 2) ibiblio (the master repo for external jars, to let the build continue even if 1 is not up-to date) 3) local repo of your superproject instance (for resolving your internal dependencies. this repo should be makred as the deploy target for jars) I don't know the details of specyfing multiple repos, and designating the deployment target for artifacts, but this is the general idea. R. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
