[kepler-dev] [Bug 3898] update .kepler instead of removing it between versions

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Thu Feb 4 12:59:21 PST 2010


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

Chad Berkley <berkley at nceas.ucsb.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |berkley at nceas.ucsb.edu
         Resolution|                            |FIXED

--- Comment #13 from Chad Berkley <berkley at nceas.ucsb.edu> 2010-02-04 12:59:19 PST ---
Matt identified these three milestones to be able to close this bug.  I believe
they are all now met.  See my comments below each.

>1. The 'install' directory can be removed and replaced by the same version of
>kepler, or by a new version, and everything still works fine
>   -- this implies that any files that should not be lost across upgrades must
>NOT be in the install directory (e.g., InstanceAuthNamespace)

This is now true.  All changeable files are now in the ~/KeplerData or the
~/.kepler directories

>2. User-created KAR files and other artifacts in the .kepler directory should
>migrate across version upgrades without duplication -- there is no need to have
>multiple copies of the same KAR file

The kar files themselves are actually not stored in the .kepler directory for
either 1.0 or 2.0.  The cached, serialized version are.  I see no way to
migrate the 1.0 serialized forms without a major headache.  I have changed the
DotKeplerManager to create a new cache directory for 2.0 if it detects that 1.0
is already installed.  I believe this to be the best workaround for this
problem. it allows 2.0 to operate correctly as well as for 1.0 to continue to
operate, albeit independently of one another.

>3. There should never be a need to 'clean' any files from the .kepler directory
>-- neither during the development cycle nor for a binary product install

I think we have finally gotten around this with some minor exceptions.  You can
now switch between suites without cleaning and the 2.0 installer will not
require a clean .kepler directory.  

I'm closing this bug.  If there is a reason for it to still be open, please
reopen with comments.

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


More information about the Kepler-dev mailing list