[
http://jira.codehaus.org/browse/MDEP-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91029
]
Gregory Kick commented on MDEP-74:
----------------------------------
while, there's not solving the runtime issue unless you started doing some
bizarre things with the classloader, wouldn't it be a much better solution for
the test dependencies to just run the same analysis against the test sources
too? it would have to be a two-pass sort of operation because you wouldn't
want to mess with the results from the main sources, but it still makes sense
to want to check your test scope...
> 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
> Fix For: 2.0-alpha-4
>
>
> 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
