oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cameron Goodale (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OODT-63) Use hard coded version numbers in shared component POMs so that MVN install works
Date Wed, 08 Dec 2010 15:52:02 GMT

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

Cameron Goodale commented on OODT-63:

I have started making these changes on my local checked out copy to try and get the mvn site
command to work.  I have replaced all references to ${oodt.version} with 0.2-SNAPSHOT.  I
will let you know if I get it to work....or if I need some help in the maven dark arts.

> 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
> 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.

View raw message