That is way better than what I was gonna do. I am looking forward to checking the code out and seeing how mvn site likes it.
Great work Brian. -C On Wed, Dec 15, 2010 at 7:07 PM, Mattmann, Chris A (388J) (JIRA) < [email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/OODT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971946#action_12971946] > > Mattmann, Chris A (388J) commented on OODT-63: > ---------------------------------------------- > > Haha, that one looks *a lot* better! I was going to ask: what's the > top-level "test" dir for? > > BTW, time to go home! :) > > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > 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. > > -- Sent from a Tin Can attached to a String
