Sure, if you'll answer this question there :) On Tue, Sep 27, 2011 at 4:50 PM, Luke Daley <[email protected]>wrote:
> Carlton, > > You are asking some very good questions that I am sure other people are > going to have in the future. > > Would you mind posting on the new forums that we are establishing to help > make the content more visible to future users? > > http://forums.gradle.org/gradle > > On 27/09/2011, at 2:55 PM, Carlton Brown wrote: > > Hi all, > > I'm trying to identify strategies to govern how Gradle handles locally > published snapshots taking priority over centrally published snapshots. > Say I have project 'A' depending on project 'B', and both are published to > my shared object repository. I want to publish B.jar locally and have A > pick up those local changes, ignoring the B.jar that gets resolved out of > the shared repository. > > This behavior was hairy to implement in ivy... basically people usually > chain the local and remote repository and then fiddle with Ivy's 100 > different knobs to make the local artifact take priority in whatever way is > desired. It was hairy and buggy and never totally satisfactory. > > Am I talking about 'project dependencies' here? What knobs are there to > control this behavior, like say to prevent a stale local artifact from > hanging around too long? > > Thanks, > Carlton > > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > >
