1) Use "mvn -X" and parse the text dependency tree to find out which dependency is pulling in the unwanted lucene artifact version. Just copy and paste the "mvn -X" output to Notepad etc and search for "lucene". Then add an <excludes> node to the offending dependency to exclude the "bad" artifact.
2) The dependency:tree mojo is not yet available in any released version. So you will need to add the Maven Snapshot repo to your pom to be able to use it. Wayne On 7/26/07, Marcelo de Barros Alcantara <[EMAIL PROTECTED]> wrote:
Hi All, I am having a problem with two dependencies (lucene 1.4.3 and lucene 2.0). They are both dependencies at some level from my "root" dependencies but the wrong classes are being called making the application unable to run. 1) Someone know how can I isolate the dependencies so that right correspondent dependencies are called? 2) I tried to use mvn dependency:tree to check the problem further but it does not work. This goal is still there? Thanks in advance for any help. Best regards, Marcelo Alcantara www.uol.com.br
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
