Re: Needed OODT Improvments
alright, On Wed, Apr 15, 2015 at 10:39 PM, Michael Starch starc...@umich.edu wrote: Dev, I've been talking with Tom and we've noted a list of things that should be improved on OODT. - pom/maven: - fix dependency circles in radix - make extra components with large number of dependencies optional (pending pull request) - move dependency versions to top-level pom making versions consistent OODT-839 - update dependency versions OODT-840 - replace xml-rpc development-only server - separate REST interfaces and client code for ops ui and cas-curator OODT 842 OODT-841 So I added the ones I said I'd do. Starch tell me when you have - fix dependency circles in radix - make extra components with large number of dependencies optional done and i'll sort out 839 and 840 but I don't want to break all your stuff. Tom - cleanup - deprecate unused or superseded sub-components - spin-off non-essential functionality into sibling projects - documentation Any thoughts? -Michael
Needed OODT Improvments
Dev, I've been talking with Tom and we've noted a list of things that should be improved on OODT. - pom/maven: - fix dependency circles in radix - make extra components with large number of dependencies optional (pending pull request) - move dependency versions to top-level pom making versions consistent - update dependency versions - replace xml-rpc development-only server - separate REST interfaces and client code for ops ui and cas-curator - cleanup - deprecate unused or superseded sub-components - spin-off non-essential functionality into sibling projects - documentation Any thoughts? -Michael
Re: Needed OODT Improvments
ACK On Wed, Apr 15, 2015 at 5:39 PM, Michael Starch starc...@umich.edu wrote: Dev, I've been talking with Tom and we've noted a list of things that should be improved on OODT. - pom/maven: - fix dependency circles in radix - make extra components with large number of dependencies optional (pending pull request) - move dependency versions to top-level pom making versions consistent - update dependency versions - replace xml-rpc development-only server - separate REST interfaces and client code for ops ui and cas-curator - cleanup - deprecate unused or superseded sub-components - spin-off non-essential functionality into sibling projects - documentation Any thoughts? -Michael -- *Lewis*
Re: Needed OODT Improvments
Sounds like some excellent maintenance activities. +1 -Cam On Wed, Apr 15, 2015 at 3:27 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: ACK On Wed, Apr 15, 2015 at 5:39 PM, Michael Starch starc...@umich.edu wrote: Dev, I've been talking with Tom and we've noted a list of things that should be improved on OODT. - pom/maven: - fix dependency circles in radix - make extra components with large number of dependencies optional (pending pull request) - move dependency versions to top-level pom making versions consistent - update dependency versions - replace xml-rpc development-only server - separate REST interfaces and client code for ops ui and cas-curator - cleanup - deprecate unused or superseded sub-components - spin-off non-essential functionality into sibling projects - documentation Any thoughts? -Michael -- *Lewis*
Re: Needed OODT Improvments
+1 to all of the below, and please turn into JIRA issues so we don’t forget Chris Mattmann chris.mattm...@gmail.com -Original Message- From: Michael Starch starc...@umich.edu Reply-To: dev@oodt.apache.org Date: Wednesday, April 15, 2015 at 5:39 PM To: dev@oodt.apache.org Subject: Needed OODT Improvments Dev, I've been talking with Tom and we've noted a list of things that should be improved on OODT. - pom/maven: - fix dependency circles in radix - make extra components with large number of dependencies optional (pending pull request) - move dependency versions to top-level pom making versions consistent - update dependency versions - replace xml-rpc development-only server - separate REST interfaces and client code for ops ui and cas-curator - cleanup - deprecate unused or superseded sub-components - spin-off non-essential functionality into sibling projects - documentation Any thoughts? -Michael
