[
https://issues.apache.org/jira/browse/OODT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Foster resolved OODT-63.
------------------------------
Resolution: Fixed
- fixed in r1050074
- with this patch applied i cleared out my maven repo and ran maven compile,
test, site all worked for me . . . however, i have some recommends for anyone
who attempts the same!!!
*Build Recommendations*
1) check out code
2) mvn compile
3) if downloading of any dependency jars stall, kill mvn compile and just rerun
it
4) mvn install
5) export MAVEN_OPTS=-Xmx2000m
6) mvn -DskipTests=true site:site
> 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
>
> Attachments: OODT-63.2010-12-15.patch.txt
>
>
> 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.
