[infinispan-dev] multiple conflicting versions as dependencies (Lucene but not only)

Hello, I'm wondering how to solve ISPN-275 (Update Lucene Directory to work with newer Lucene versions v.3.0.x) The Lucene Directory works fine with latest Lucene 3.0.2, my doubt is if I should bump the dependency version to that the tests are really running against 3.0.2; they are currently run against 2.9.3. The property <version.lucene> was local to the LD module only, to not interfere with a potential different version in other modules: the Query module is depending on Search 3.2 which needs Lucene 2.9.x (and is not 100% compatible with 3.0.x). So until Hibernate Search is able to deal properly with the newer Lucene we should use 2.9.x as main reference, but for all potential users using the newer Lucene I think we should have the Lucene Directory module tested on 3.0.x too - not an easy feat with Maven AFAIK. Being compatible with Hibernate Search is not the only reason, as the directory works fine with all Lucene versions from 2.4 to 3.x it's useful to a broader range of users: Lucene's API changes are relevant and intrusive, it's not easy to jump from 2.4 to 3 for existing applications, for this reasons it's imho a great value if we keep it tested against both branches of Lucene, at least for some time. As said, no code changes are needed; the easy way is to add a Hudson target using "mvn clean test -Dversion.lucene=3.0.2", I could add a profile for that, but still you have to invoke the build twice. I wonder if someone has better ideas? As a side note, I noticed an additional inconsitency: the parent pom.xml defines a dependency to javax.persistence:1.0 used by infinispan-jopr-plugin but Search is going to introduce in classpath hibernate-jpa-2.0-api; also this module is tested with hibernate-core 3.3.1; wouldn't this need to be tested by the same versions introduced by the Query module?