[
https://issues.apache.org/jira/browse/OODT-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893526#action_12893526
]
David Woollard commented on OODT-15:
------------------------------------
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
> One trunk for all OODT components with top level build
> ------------------------------------------------------
>
> Key: OODT-15
> URL: https://issues.apache.org/jira/browse/OODT-15
> 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 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
