[
https://issues.apache.org/jira/browse/MDEP-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MDEP-269.
-------------------------------
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.
> Goal to convert a legacy /lib/*.jar to maven dependencies list
> --------------------------------------------------------------
>
> Key: MDEP-269
> URL: https://issues.apache.org/jira/browse/MDEP-269
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Reporter: nicolas de loof
> Priority: Minor
> Attachments: MDEP-269.patch
>
>
> To convert a legacy ant/script-based project to Maven first step is to
> identify all dependencies as maven artifacts. This can be long and subject to
> errors.
> Using Nexus index [1], Nexus REST API [2], or any other tooling, the plugin
> could automagically search the available repositories for known artifacts to
> match the content of a /lib directory, and output a POM formatted list of
> dependencies, also warning for unresolved ones.
> alf-maven-osecm plugin allready provides such feature using a custom CSV
> format, this code can be used as a dev sample.
> [1] http://www.sonatype.com/people/2009/06/nexus-indexer-api-part-2/
> [2] https://docs.sonatype.com/display/NX/Nexus+Rest+API
> [3]
> http://alf-maven-osecm.googlecode.com/svn/trunk/dependenciesGenerator-maven-plugin/dependenciesGenerator-maven-plugin/
> http://opensourceecm.fr/maven/dependenciesGenerator/index.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
