: Is there a set of tests in the Lucene sources I could use to test the : "JBCDirectory", as I call it? Perhaps something way I could change the "index : store provider" and re-run some existing tests, and perhaps add some clustered : tests specific to my plugin?
I think most of the existing tests have the Directory impl hardcoded in them ... the best thing to do might be to refactor the existing tests so Directory creation comes from an overridable function in a subclass... come ot think of it, Karl may have already done this as part of his InstantiatedIndex patch (check jira) but i'm not sure ... the conversation sounds familiar, but i think he was looking at facading the entire IndexReader impl not just the directory, so any refactoring approach he might have taken may not have gone far enough to work in this case. It would certianly be nice if there was an easy way to run every test in the test suite against an arbitrary Directory implementation. : Finally, regarding hosting, I am happy to contribute this to Lucene (alongside : the JEDirectory, etc) but if licensing (JBoss Cache is LGPL, although the : plugin code can be ASL if need be) or language levels (the plugin depends on : JBoss Cache 2.x, which requires JDK 5) then I'm happy to host the plugin : externally. contribs can run require 1.5 already ... an soon the trunk will move to 1.5 so that's not really an issue, the licensing may be, but it depends on how the integration with JBoss winds up working (ie: i don't know if having the build scripts download JBoss at build time to compile against them is allowed or not) -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
