I would be curious if you could unpack you app and just replace the JARs with ones from Maven repo's and have it still work.
I can't tell you how projects I've encountered where I cannot figure what version a JAR is or where it came from. I am sure I have seen hand modified JAR lumping packages together or JARs from IDE libraries that aren't intended for distribution. I have used the technique described here but I have also had too to forensic type package level comparisons to try an find matches. Eventually slugging our way through namespace collisions and knocking down issues one Classpath Not Found at a time. > -----Original Message----- > From: Brian Topping [mailto:[email protected]] > Sent: Wednesday, November 10, 2010 3:49 PM > To: Maven Users List > Subject: Re: Figuring out the proper Maven dependency setting > > > On Nov 10, 2010, at 3:40 PM, marshall wrote: > > > Hi; > > This is probably a beginner question, but I thought it was > worth posing because it is frequently very frustrating when > working with Maven. > > Is there a clear way to know which particular dependencies > Maven requires, when working with a set of jars/libraries? > > This isn't as much a Maven question as it is a question on > the organizations that package the dependencies, but here's > some info. Dependencies typically depend on other > dependencies, and one eventually gets a transitive closure of > dependencies. You can see this in your build by running 'mvn > dependency:tree'. This will show you a tree of who is pulling > in what, and help make decisions on what to pull in at the > top level and what you can ignore. > > For instance, if you used to pull in asm for use with > Hibernate, you can stop doing that, because the Hibernate > dependency you choose will know better what exact version it > was compiled at. If you need a specific version of asm for > your own needs, this is where things get more complicated. > > These problems existed before Maven though. Maven just gives > you a bigger, more efficient gun to shoot yourself in the foot with. > > Hope that helps... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
