On 5/29/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 5/29/07, Jeff Mutonho <[EMAIL PROTECTED]> wrote:
> Thanks.With Maven its always a path of discovery :).Anyway it seems
> like there's some other library that depends on xml-apis , as
> excluding it from commons-logging and jaxen didn't resolve the issue.
Did you do a clean build? If not, the file will still be in
WEB-INF/lib under target and will show up in the war.
You can run mvn with -X on the command line and look at the indented
output to find out where the unwanted jar is coming from.
There is also an html formatted dependencies report that's part of the
project-info-reports plugin. mvn project-info-reports:dependencies
... and look at target/site/dependencies.html
http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies-mojo.html
--
Wendy
I generated the project website and checked the dependency graph for
the war project , which showed the following :
za.co.pragmatix.portal:portal-webservices:jar
* dom4j:dom4j:jar
o xml-apis:xml-apis:jar
I then added the xml-apis exclusion to the pom , did a clean build and
problem solved.
Thanks everyone...:)
"Don't take the name of root in vain."
Jeff Mutonho
Cape Town
South Africa
GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
