Hi! As I commented on the JIRA ISSUE JCR-352 there is only a compilation problem of Jackrabbit against Lucene 1.9.1. Still, there are 76 more deprecation warnings. Here are some details about them:
org.apache.lucene.index.IndexReader.delete(Term): recommended change IndexReader.deleteDocuments(Term): unavailable in 1.4.3 org.apache.lucene.index.IndexWriter.minMergeDocs, maxMergeDocs,mergeFactor,infoStream deprecated in favour of IndexWriter.setX: unavailable in 1.4.3 o.a.l.store.OutputStream; org.apache.lucene.store.InputStream deprecated in favour of new classes unavailable in 1.4.3 o.a.l.store.Directory.createFile and openFile deprecated in favour of createOutput/openInput: unavailable in 1.4.3 o.a.l.search.BooleanQuery.add(Query, boolean, boolean) deprecated in favour of add(Query, BooleanClause.Occur: unavailable in 1.4.3 constructor o.a.l.document.Field(String, String, boolean, boolean, boolean) deprecated in favour of ctor (String, String, Field.Store, Field.Index): unavailable in 1.4.3 o.a.l.document.Field.Text(String, Reader) deprecated in favour of ctor Field(String, Reader): unavailable in 1.4.3 o.a.l.search.BooleanClause.prohibited and required deprecated in favour of setters: unavailable in 1.4.3 o.a.l.search.BooleanClause(Query, boolean, boolean) deprecated in favour of ctor (Query, BooleanClause.Occur): unavailable in 1.4.3 o.a.l.document.DateField deprecated and recommended usage way in another API. Still the comment says that this class will not be removed in near future even if deprecated. As you can see, having Jackrabit work with Lucene 1.9.1 is an easy job. Unfortunately, a future upgrade to Lucene 2.0 (that will probably remove some of this deprecated API) will be more complex and will create important backwards compatibility problems. hth, ./alex -- .w( the_mindstorm )p.
