You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matthew Beermann (JIRA)" <ji...@codehaus.org> on 2007/03/21 16:30:34 UTC
[jira] Commented: (MDEP-74) dependencies in test scope are not
handled properly by analyze
[ http://jira.codehaus.org/browse/MDEP-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90712 ]
Matthew Beermann commented on MDEP-74:
--------------------------------------
It also doesn't deal well with Service Provider Interfaces (SPI), which are implementations for a given interface that are loaded dynamically at runtime. The code shouldn't and doesn't compile directly against the implementation, but they ARE needed at test time. So, they show up as false positives in unused declared dependencies.
Should the test scope perhaps just be ignored entirely?
> dependencies in test scope are not handled properly by analyze
> --------------------------------------------------------------
>
> Key: MDEP-74
> URL: http://jira.codehaus.org/browse/MDEP-74
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: analyze
> Affects Versions: 2.0-alpha-3
> Environment: os x 10.4.9, java 1.5.0_07-87, maven 2.0.5
> Reporter: Gregory Kick
> Assigned To: Brian Fox
>
> dependency:analyze doesn't recognize test sources for dependencies with test scope because despite having numerous unit tests, it lists junit as an unused dependency.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira