[jira] Commented: (OODT-63) Use hard coded version numbers in shared component POMs so that MVN install works

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

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

Chris A. Mattmann commented on OODT-63:
---------------------------------------

Note, this is what I think we're seeing:

http://jira.codehaus.org/browse/MNG-3782

> Use hard coded version numbers in shared component POMs so that MVN install works
> ---------------------------------------------------------------------------------
>
>                 Key: OODT-63
>                 URL: https://issues.apache.org/jira/browse/OODT-63
>             Project: OODT
>          Issue Type: Improvement
>          Components: build proces
>    Affects Versions: 0.1-incubating
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>            Priority: Critical
>             Fix For: 0.2-incubating
>
>
> As it turns out, good ol' Maven doesn't allow POMs with ${variables} for version #s to allow their ${version}s to be resolved dynamically at runtime. In practical terms what this means it that currently the OODT jars can't be published, e.g., to Maven Central, because you get a whole bunch of warnings about not being able to download oodt-core-${oodt.version}.
> This can be remedied by not being as slick when it comes to variable management in the POMs, and simply by putting the actual POM version in all dependent POMs within the OODT build.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.