To phrase the question a little differently, how do you upgrade OODT in a project? Do you need to download the new source/Radix distribution and copy over configuration files? Or, could we make it more modular?
Tyler On Sun, Feb 22, 2015 at 6:00 PM, Mattmann, Chris A (3980) < [email protected]> wrote: > Hey Val, > > My general practice is to maintain config files along with each > RADIX deployment now, but in the past, I was known to maintain a > thin, minimal OODT project in Github and/or SVN and then to have > like an Maven/Ant integration script that runs RADIX, (or formerly > before it existed did a bunch of SVN/Git checkouts and builds) and > then overlays my config on top. You can see a similar example of > how to run things from Ant/Maven here: > > http://svn.apache.org/repos/asf/oodt/tools/depfixer/ > > > Cheers, > Chris > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Chief Architect > Instrument Software and Science Data Systems Section (398) > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 168-519, Mailstop: 168-527 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Associate Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > > -----Original Message----- > From: <Mallder>, Valerie <[email protected]> > Reply-To: "[email protected]" <[email protected]> > Date: Tuesday, February 17, 2015 at 11:46 AM > To: "[email protected]" <[email protected]> > Subject: how do you manage OODT files vs. project-specific files? > > >Hi All, > > > >I am looking for some advice, so please respond if you have ideas on this > >topic. > > > >Assuming you are using OODT, or developing OODT, to support a totally > >different project that you are working on in your day job, how do you > >manage all of your OODT files vs. all of your project-specific files? I > >am looking for real-life examples of how people are configuration > >managing their files. > > > >I am using the deployed RADiX Archetype, which suggests that I keep my > >project specific files in an 'oodt/extensions' directory. However, I > >have also made changes to some OODT configuration and policy files such > >as workflow/policy/tasks.xml and workflow/policy/events.xml, etc. > > > >If I wanted to upgrade to a new version of the RADiX Archetype and deploy > >a new release of the RADiX Archetype over top of my current version, then > >all of my changes to the tasks.xml and events.xml files would be lost. > > > >What is your favorite way of managing your OODT installations so that > >changes you have made to the configuration files and policy files > >located in each OODT application's directory tree are not overwritten? > >(Ideally, I wish I could keep all of my project-specific and changed > >files outside of the each OODT application directory tree, but it doesn't > >sound like anyone does this.) > > > >Thanks, > > > >Val > > > >P.S. I have managed large software systems before, but they were > >different from OODT in that > > > > > > > >Valerie A. Mallder > > > >New Horizons Deputy Mission System Engineer > >The Johns Hopkins University/Applied Physics Laboratory > >11100 Johns Hopkins Rd (MS 23-282), Laurel, MD 20723 > >240-228-7846 (Office) 410-504-2233 (Blackberry) > > > >
