[ChangeLog] Destroy() method semantic

[Emmanuel Lecharny]

Hi,

I'm looking at the MemoryChangeLogStore, and the destroy() method
implementation do a full save on disk :

public void destroy() throws Exception
{
    saveRevision();
    saveTags();
    saveChangeLog();
}

Is there any reason to do that ? Shouldn't we remove everything
instead of saving data ?

It's not necessarily important for the memory CL, but for a disk CL,
we have to decide what is the exact semantic of this method.


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com