[
http://jira.codehaus.org/browse/MDEP-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129043#action_129043
]
Brian Fox commented on MDEP-158:
--------------------------------
Yes, if we structure this like this other goals in the plugin, it will inherit
the rest of the artifact filtering logic so you could narrow down the search
any way you wish (scope/type/name/group/classifier etc). This sounds like a
useful goal.
> find a resource on the classpath and show which jar it comes from and the
> dependency path to it
> -----------------------------------------------------------------------------------------------
>
> Key: MDEP-158
> URL: http://jira.codehaus.org/browse/MDEP-158
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Reporter: james strachan
> Assignee: Brian Fox
>
> I blogged about this here :
> http://macstrac.blogspot.com/2008/03/lazyweb-maven-plugin-to-find-resources.html
> Steve commented that <whichsource> the Ant task does a similar kinda thing.
> So I'd like to be able to go to any maven projectl and type...
> mvn dependency:resource -Dresource=log4j.properties
> and it'd list the jars it finds the resource in along with the transitive
> dependency path etc.
> This would be amazingly useful for diagnosing which jars accidentally ship a
> log4j.properties file - say
--
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
