Hi, Thanks for the explanation.
I am still not convinced that it is a good idea to add something from testing to "production" just to workaround some test-performance issues on a single platform.... This is just something more to maintain and explain ... Regards Felix Marcel Reutegger schrieb: > it's an in-memory journal implementation that's currently located in > the test sources. there are already two other implementations, one is > file based and the other uses a database. there are also a number of > in-memory implementations of modules: a persistence manager, a > filesystem, a lucene directory manager. I don't think there's anything > wrong with having one for the journal. it's sure not recommended to be > used in a production environment but that's already documented. > > regards > marcel > > On Mon, Jul 6, 2009 at 10:01, Felix Meschberger<[email protected]> wrote: >> Just to be sure (it sounds so wrong ;-) ): You want to move a test class >> in to the main source tree and thus add to the runtime library ? >> >> Regards >> Felix >> >> Marcel Reutegger (JIRA) schrieb: >>> Move MemoryJournal from test to main >>> ------------------------------------ >>> >>> Key: JCR-2189 >>> URL: https://issues.apache.org/jira/browse/JCR-2189 >>> Project: Jackrabbit Content Repository >>> Issue Type: Improvement >>> Components: jackrabbit-core >>> Reporter: Marcel Reutegger >>> Priority: Minor >>> >>> >>> Running our tests with the FileJournal implementation on a windows box can >>> be quite slow because of the many FileDescriptor.sync() calls. >>> >>> I'd like to move the MemoryJournal in jackrabbit-core test to the main >>> sources. That way we can use it in other test setups. >>> >
