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

        Hide
        Chris A. Mattmann added a comment -

        Hey Guys,

        Let me take a crack at this – I should have some time today or tomorrow.

        Thanks!

        Cheers,
        Chris

        Show
        Chris A. Mattmann added a comment - Hey Guys, Let me take a crack at this – I should have some time today or tomorrow. Thanks! Cheers, Chris
        Hide
        Chris A. Mattmann added a comment -

        As of r940703, we're pretty close. I just need to:

        • fix the package structure to match org.apache.oodt.*
        • fix MVN top-level build
        Show
        Chris A. Mattmann added a comment - As of r940703, we're pretty close. I just need to: fix the package structure to match org.apache.oodt.* fix MVN top-level build
        Hide
        Chris A. Mattmann added a comment -
        • set fix version
        Show
        Chris A. Mattmann added a comment - set fix version
        Hide
        David Woollard added a comment -

        I just committed r980323, which is closer still.

        The top level build works minus the following:

        1) three components are not building and are currently commented out: catalog, pushpull and webapp-fmprod
        2) there are four current build-time deps that cannot be found using a clean mvn repo:
        com.hp.hpl:jena:jar:1.6.1
        com.oracle:ojdbc:jar:14
        xmlrpc:xmlrpc:jar:2.1-dev
        apache:tika:jar:0.2-fork

        Show
        David Woollard added a comment - I just committed r980323, which is closer still. The top level build works minus the following: 1) three components are not building and are currently commented out: catalog, pushpull and webapp-fmprod 2) there are four current build-time deps that cannot be found using a clean mvn repo: com.hp.hpl:jena:jar:1.6.1 com.oracle:ojdbc:jar:14 xmlrpc:xmlrpc:jar:2.1-dev apache:tika:jar:0.2-fork
        Hide
        Chris A. Mattmann added a comment -

        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)

        Cheers,
        Chris

        Show
        Chris A. Mattmann added a comment - 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) Cheers, Chris
        Hide
        David Woollard added a comment -

        Thanks Chris! I made your recommended changes in r980343.

        Show
        David Woollard added a comment - Thanks Chris! I made your recommended changes in r980343.
        Hide
        David Woollard added a comment -

        Since I resolved OODT-24, I have added back weapp-fmprod to the top level build.

        Show
        David Woollard added a comment - Since I resolved OODT-24 , I have added back weapp-fmprod to the top level build.
        Hide
        Chris A. Mattmann added a comment -
        • I'm calling it done. We've got a top-level build; we've got a process for building out all the components. We're there.
        Show
        Chris A. Mattmann added a comment - I'm calling it done. We've got a top-level build; we've got a process for building out all the components. We're there.

          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