I'd guess not. Feel free to try upgrading the lucene version and see what happens. I dug around and I think these commits will fix the source code incompatibilities when moving from lucene 3.0.1 to 3.1.0:
https://github.com/neo4j/community/commit/931bdb49d2017e11440bf588bc170a68f09a83b2 https://github.com/neo4j/community/commit/8e48d15320bc0cde1d03a9994bc3d68637a0dce1 https://github.com/neo4j/community/commit/cccd54d55efe15e4293609cf019f63a4716799b3 even if the first one is a bit entangled in some other changes and I saw that some of those had trouble being applied, but it still worked at a first glance. It's a start at least. Best, Mattias 2011/6/20 Rick Bullotta <[email protected]> > Other than testing, is there any reason that Neo4J 1.3 *wouldn't* work with > Lucene 3.1.0? > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [[email protected]] Hacker, Neo Technology www.neotechnology.com _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
