Your pom.xml should declare all dependency versions explicitly. And to prevent any changes, do not use any snapshots. Furthermore, use dependency:analyze on your project to make sure all libraries in use are explicitly declared. After you lock them all down, tell your developers not to update the pom.xml file. That will ensure it.
Cheers, Paul On Mon, Nov 3, 2014 at 10:33 PM, Irfan Sayed <[email protected]> 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 >
