[kepler-dev] changing suites with new changes

[Aaron Schultz]

Chad, no definitely not, the whole point of the persistent directory is 
that it never gets deleted or removed.  Perhaps we need to store the 
configuration information in the transient module directory...  Or the 
build system needs to delete just the configuration directories when the 
suite is changed...  or some other solution.

Aaron

Chad Berkley wrote:
> Hi,
>
> A few things have changed in the last couple days.  For one, the 
> persistent (non-cache) data is now being stored in ~/KeplerData 
> instead of .kepler/persistent.  The 2nd thing that has changed is that 
> I changed the configuration manager to automatically save 
> configurations as they change.  Because of this, you may see errors 
> when you change between suites becuase the configuration manager will 
> (correctly) read the config files in the KeplerData directory which 
> might have incorrect configuration data for the suite you have changed 
> to.
>
> The error I ran into was when I switched from wrp to kepler.  Because 
> the wrp suite adds additional kar handlers that kepler does not have, 
> I get a classNotFoundException on startup.  This can be remedied by 
> removing your KeplerData/modules directory when you switch between 
> modules.  I can change the clean-all build command to do this 
> automatically if everyone agrees that this directory should be removed 
> with a clean-all.
>
> Just a heads up.
>
> chad
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>