OODT
  1. OODT
  2. OODT-15

One trunk for all OODT components with top level build

    Details

      Description

      Per Brian Foster's discussion with Chris Mattmann (IF CONVINCING ARGUMENTS AGAINST THIS PROPOSAL ARE NOT IN BY NEXT WEEK, I WILL BEGIN IMPLEMENTATION):

      • 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

        Activity

          People

          • Assignee:
            Chris A. Mattmann
            Reporter:
            Brian Foster
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development