You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2016/01/12 21:12:46 UTC

[jira] [Closed] (MDEP-158) find a resource on the classpath and show which jar it comes from and the dependency path to it

     [ https://issues.apache.org/jira/browse/MDEP-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MDEP-158.
-------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still persists, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> find a resource on the classpath and show which jar it comes from and the dependency path to it
> -----------------------------------------------------------------------------------------------
>
>                 Key: MDEP-158
>                 URL: https://issues.apache.org/jira/browse/MDEP-158
>             Project: Maven Dependency Plugin
>          Issue Type: Improvement
>            Reporter: james strachan
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)