[jira] Commented: (OODT-137) OODT 0.1-incubating dependency fixer tool

["Rishi Verma (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OODT-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993168#comment-12993168 ] 

Rishi Verma commented on OODT-137:
----------------------------------

Usage guide available here: https://cwiki.apache.org/confluence/display/OODT/Using+OODT+0.1-incubating+dependency+fixer+tool

> OODT 0.1-incubating dependency fixer tool
> -----------------------------------------
>
>                 Key: OODT-137
>                 URL: https://issues.apache.org/jira/browse/OODT-137
>             Project: OODT
>          Issue Type: Improvement
>          Components: build proces
>    Affects Versions: 0.1-incubating
>         Environment: Maven 2.2.0, Ant 1.7.1, Java 1.6
>            Reporter: Rishi Verma
>            Priority: Minor
>             Fix For: 0.2
>
>         Attachments: oodt-0.1-incubating-depfixer.tar
>
>
> Since OODT 0.1-incubating dependency jars are not published to Maven central, the user requires these jars to be installed locally. Furthermore, certain versions of maven cannot properly interpret the ${oodt.version} string used by component poms when installing them. This issue has been fixed within OODT 0.2 (https://issues.apache.org/jira/browse/OODT-63). However for OODT 0.1-incubating, a solution is still required. The dependency fixer tool addresses this need. 
> The dependency fixer tool performs three steps:
> 1) Download specified OODT 0.1-incubating component projects from the apache repo
> 2) Replace ${oodt.version} string within pom files with '0.1-incubating'
> 3) Install corrected pom to user's local mvn repo
> The dependency fixer tool could potentially be incorporated within: http://svn.apache.org/repos/asf/oodt/tools package.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira