[OODT-63] Use hard coded version numbers in shared component POMs so that MVN install works

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.1-incubating
• Fix Version/s: 0.2
• Component/s: build proces
• Assignee: Chris A. Mattmann
• Reporter: Chris A. Mattmann
• Created: 21/Nov/10 02:00
• Updated: 16/Dec/10 17:54
• Resolved: 16/Dec/10 17:54

Description

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.