Thanks for clarifying Enis, this makes it crystal clear. It was more a curiosity I had, and as you make it explicit that we need to manually ensure each dependency version is in line with the project, now I understand exactly where you are coming from.
Thank you On Thu, Oct 20, 2011 at 5:58 PM, Enis Söztutar <[email protected]> wrote: > Hi, > > In the ivy setup, org.apache.gora dependencies are resolved locally, which > is declared in ivy-settings.xml. So, the gora-core dependency with the > latest.integration will resolve to the latest local version, which should > be > in ~/.ivy2/local/org.apache.gora/gora-core/ > > But, for managing dependencies for the project for external libraries, we > want to explicitly state the version of the library, since we do want to > control which binary goes in to the build. Why do you want to grab the > latest version? > > Thanks, > Enis > > On Thu, Oct 20, 2011 at 9:51 AM, lewis john mcgibbney < > [email protected]> wrote: > > > Hi, > > > > With regards to managing dependencies, I've been looking (elsewhere) for > a > > solution to keeping on top of every changing dependency upgrades/updates. > A > > simple question really... does the rev value in the snippet below > > automatically grab the 'most recent' version of that particular > dependency > > from repository.apache.org ? > > > > Thanks > > > > <dependency org="org.apache.gora" name="gora-core" > rev="latest.integration" > > changing="true" conf="*->@"/> > > > > -- > > *Lewis* > > > -- *Lewis*
