Yes, that's how it works. /Anders (mobile) Den 4 nov 2014 06:06 skrev "Irfan Sayed" <[email protected]>:
> so, lets say if i am using x dependency with version 1.1 and if the > developer changes the code of that dependency, keeping the same version as > 1.1 > then nexus will not download the latest code changes for that dependency > because the version still refers to 1.1 ??? > if that is the case, this is really nice > > regards > > > On Tue, Nov 4, 2014 at 10:20 AM, Ron Wheeler < > [email protected] > > wrote: > > > Have you scanned the Maven books referenced on the Maven web site? Best > > starting place. > > > > With a repository (Nexus), people are prevented from deploying the same > > version twice so you are guaranteed that if you build with version 2.3.15 > > of ourNiceUtility, you will always get the same code. The repo will > simply > > not allow them to overwrite version 2.3.15 once it is deployed into the > > wild(public). > > > > Beats firing developers but stops them from doing silly things. > > > > > > > > On 03/11/2014 11:33 PM, Irfan Sayed wrote: > > > >> hello, > >> > >> is there any good doc/blog which describes the handling of explicit > >> declaration of dependencies. > >> when we build the code, we use certain dependencies , how we can make > sure > >> that when we reproduce the same build after the gap of 6 months , same > and > >> exact dependencies will be used. ??? > >> i know we can have artifactory/nexus , but that does not guarantee the > >> exact version of dependency when developer changes the code and make it > >> public keeping the version same > >> > >> please suggest > >> > >> regards > >> > >> > > > > -- > > Ron Wheeler > > President > > Artifact Software Inc > > email: [email protected] > > skype: ronaldmwheeler > > phone: 866-970-2435, ext 102 > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
