Hi, If you decide to include the transient dependencies, a plugin called deptools can help you detect when wrong dependency-versions are chosen.
You can have a look at it here: http://github.com/mbknor/deptools <http://github.com/mbknor/deptools>Regards, Morten On Tue, May 18, 2010 at 2:42 PM, AVSUNIL <[email protected]> wrote: > > Hi, > > I have project A which produces artifact as war. Project A has dependency > on > project B and it is mentioned in the pom of Project A. Now the build of > Project A is acting indifferently in 2 environments > > a) When I am building from my local/development envionment, it builds the > war with only the dependencies mentioned in its pom > > b) When I build from my test environment, it builds the war with > dependecies > mentioned in pom as well as dependecies of dependecies. This is undesirable > as war will become very big as well as unwanted versions might cree through > > How do I get the behaviour of my dev env in test env also? How do I make > sure dependecies of dependencies does not come inot my war? > > I am only using pom and and not the assembly descriptor. > > Both environment have the same build script which checksout the latest > > from SVN and then does > mvn clean > mvn compile > mvn package > > Thanks > Sunil > > -- > View this message in context: > http://old.nabble.com/Is-there-a-way-to-disable-transitive-dependencies--tp28595375p28595375.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
