Grzegorz Kossakowski wrote:
Kamal pisze:
Carsten Ziegeler wrote:
Grzegorz Kossakowski wrote:
Kamal pisze:
Grzegorz Kossakowski wrote:
Kamal pisze:
I tried to check out the dependencies (using mvn
dependency:list) to work out where the conflict is happening,
and maven couldn't find the dependency plugin. Any thoughts?
Weird. What about:
mvn dependency:list -U
Nope.
Then, to be honest I have no clue. Are you sure that Maven has no
network problems?
Try
mvn org.apache.maven.plugins:maven-dependency-plugin:2.0:list
Thanks. That seems to work. Why do I have to do this extra guff?
At any rate, I got my output. What I don't understand is I have this:
[INFO] commons-collections:commons-collections:jar:3.2:compile
If I am reading this (and this:
http://commons.apache.org/collections/api-3.2/org/apache/commons/collections/map/MultiValueMap.html)
right, then I have the right JAR file. I checked the target
directory, and the JAR file is there.
Am I still missing something?
You said earlier that you included dependency to commons-collections
manually to your POM file. Are you sure you are running mvn
dependency:list with POM not containing explicit dependency on
collections?
If so, then it's all very weird. If you see jar in target directory
then it should be included into the classpath as well. Anyway, you can
always check the classpath using:
mvn jetty:run -X
I will give this a go. I actual fact, I probably should be focussing on
the issue of packaged wars.
Hope that helps.
BTW. What version of Maven do you use?
2.0.4
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
