[
http://jira.codehaus.org/browse/MDEP-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof updated MDEP-269:
---------------------------------
Description:
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
was:
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/
> Goal to convert a legacy /lib/*.jar to maven dependencies list
> --------------------------------------------------------------
>
> Key: MDEP-269
> URL: http://jira.codehaus.org/browse/MDEP-269
> Project: Maven 2.x Dependency Plugin
> Issue Type: New Feature
> Reporter: nicolas de loof
> Assignee: Brian Fox
> Priority: Minor
>
> 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 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
