[kepler-dev] on your next kepler update

[Aaron Schultz]

Hi Chad,

The InstanceAuthNamespace file contains a java serialized string for the 
unique authority and namespace of any given kepler installation (which 
is either retrieved from a webservice or assigned via UUID).

For each installation of kepler on a given machine there would be 
(actually there now is) a subdirectory in the .kepler directory that was 
named using the authority and namespace.
Each of these .kepler/instance directories would contain it's own cache 
as we discussed yesterday....

So we need that one file to find all the other files for any given 
installation of kepler...

Aaron

Chad Berkley wrote:
> Hi Aaron,
>
> I've been seeing this file appear and wondering what it was.  I think 
> things like this should be written to .kepler or some other user 
> directory.  I agree with David that the kepler project directory 
> should probably not be written to in general.  Maybe this type of file 
> should be written to the cache so that it could be programatically 
> purged if and when it needs to be.
>
> thanks,
> chad
>
>
> David Welker wrote:
>> Hi Aaron,
>>
>> In general, you need to avoid writing anything to the kepler.modules 
>> project root directory. In the general case, this directory is likely 
>> to be stored in a read-only area of disk.
>>
>> David
>>>
>>> You will want to delete the InstanceAuthNamespace file in your 
>>> project root directory.
>>>
>>> Otherwise you will have troubles getting proper object ids for LSIDs.
>>>
>>> Aaron
>>> _______________________________________________
>>> Kepler-dev mailing list
>>> Kepler-dev at kepler-project.org
>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>>
>>
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>