[
https://issues.apache.org/jira/browse/MDEP-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MDEP-289.
----------------------------------------
Resolution: Invalid
The issue here is in the maven-dependency-analyzer and tracked under
https://issues.apache.org/jira/browse/MSHARED-47. That's what needs work. No
changes are needed in the plugin aside from updating to a fixed analyzer.
> Incorrect warning with javax.xml
> --------------------------------
>
> Key: MDEP-289
> URL: https://issues.apache.org/jira/browse/MDEP-289
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
> Affects Versions: 2.1
> Environment: OS : Windows XP
> Maven 2.2.1
> Java 1.5
> Reporter: zaccret
> Assignee: Elliotte Rusty Harold
> Priority: Major
> Labels: S2, intern
> Attachments: sandbox.zip
>
>
> When you use some javax.xml classes in a project and that you have transitive
> dependencies containing these classes, you will get a warning if you analyze
> your dependencies (Used undeclared dependencies found), even if the classes
> you use are contained in your JDK.
> I attach a project using javax.xml.parsers.DocumentBuilder which is included
> in Java Class Library (rt.jar) but also in a transitive dependency (xml-apis).
> I think we should not get a warning because the Java Class Library should be
> the first library found in the classpath, doesn't it ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
