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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
