: build and nicely gets all dependencies to Lucene and Tika whenever I build : or release, no problem there and certainly no need to have it merged into : Lucene's svn!
The key distinction is that Solr is allready in "Lucene's svn" -- The question is how reorg things in a way that makes it easier to build Solr and Lucene-Java all at once, while wtill making it easy to build just Lucene-Java. : Professionally i work on a (world-class) geocoder that also nicely depends : on Lucene by using maven, no problems there at all and no need to merge : that code in Lucene's svn! Unless maven has some features i'm not aware of, your "nicely depends" works buy pulling Lucene jars from a repository -- changing Solr to do that (instead of having committed jars) would be farrly simple (with or w/o maven), but that's not the goal. The goal is to make it easy to build both at once, have patches that update both, and (make it easy to) have atomic svn commits that touch both. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
