I'm the one who originally lobbied for this patch to get the number of patches required to compile Java Lucene (from .class files) with gcj down a bit. I've since switched away from gcj, using jcc [1] instead which I wrote for PyLucene originally. That being said, if I were still using gcj today, I'd lobby against removing these patches as it can take years before a given gcj release stabilizes on more "arcane" platforms (read non-Linux) such as Mac OS X or Windows. I regularly see people asking gcj 3.x questions on the gcj mailing list. They're not getting any help but still, it shows the inertia in upgrading to newer releases. In other words, assuming that the world has had two months to switch to gcj 4.3.1 and can use it happily on their platform of choice is rather optimistic. If people are using gcj to compile Lucene, reverting this patch now is like pulling the rug from under their feet. >From PyLucene's standpoint, PyLucene-with-GCJ has been deprecated for almost a year now and these patches can go. From a wider perspective, I'm not so sure. Andi.. [1] http://svn.osafoundation.org/pylucene/trunk/jcc/ --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org