[kepler-dev] [Bug 4578] tracking bug for changes to .kepler

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4578

--- Comment #5 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2010-02-05 14:27:07 PST ---
I'm ok with that -- I was erroneously thinking the build system deleted all of
.kepler with ant clean-cache.(In reply to comment #4)

> the upgrade work I did happens in two parts:
> 
> First, if DotKeplerManager (DKM) sees the directory signature of a 1.0 .kepler
> directory, it renames the kepler 2.0 cache directory to 'cache-2.0.0'.  It then
> sets kepler 2.0 to use that cache dir.  That dir can be removed at anytime.  
> 
> The second thing it does is to add a versionMarker file.  The version marker
> serves two purposes.  It saves the version number of the latest version of
> kepler to use the directory, and it also writes any changes to the DKM
> variables that result from an upgrade.  I did this just to save cycles in
> determining and redetermining if the directory names should be changed.  If the
> version marker is removed, it will be recreated.  
> 
> I decided to do this instead of making a .kepler2 directory just because I
> thought it might be annoying to have more than one directory around.  It seems
> like we will also end up with .kepler3 and .kepler4, etc in the future, which
> is not desirable (IMHO).  It is still totally possible (and easy) (if anyone
> has a good reason to do it that way) to use .keplerX instead of the way I did
> it.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.