incubator-oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <>
Subject [jira] Commented: (OODT-15) One trunk for all OODT components with top level build
Date Thu, 29 Jul 2010 06:39:17 GMT


Chris A. Mattmann commented on OODT-15:

Hey Dave,

The fix for 2c and 2d is as follows:

2c: xmlrpc=>2.0.1
2d: tika=>0.3 (I included TIKA-194 in that release which was the only reason we worked
0.2 internally at JPL back in the day)


> One trunk for all OODT components with top level build
> ------------------------------------------------------
>                 Key: OODT-15
>                 URL:
>             Project: OODT
>          Issue Type: Improvement
>          Components: crawler, file manager, pge wrapper framework, product server, profile
server, push pull framework, query server, resource manager, workflow manager
>         Environment: none
>            Reporter: Brian Foster
>            Assignee: Chris A. Mattmann
>            Priority: Minor
>             Fix For: 0.1-incubating
> Per Brian Foster's discussion with Chris Mattmann (IF CONVINCING ARGUMENTS AGAINST THIS
> - OODT will have one trunk with a directory for each component (i.e. filemgr, workflow,
resource, etc . . .): <oodt-base>/trunk/<oodt-component>
> - OODT will have one tags: <oodt-base>/tags/<oodt-version>/<oodt-component>
> - OODT branches is TBD -- however, when branches are merged with trunk, they must be
updated to work with all other components in trunk or other components updated to work with
branch or both.
> - Rational: This will solve the common problem of cross component jar deps conflicts,
it will also clarify the common issue of knowing which OODT components are compatible, and
allow for a top level build.
> NOTE: This will require a synch of all OODT component versions on future tag release

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

View raw message