Ah, I think the light finally dawns. And helps explain why I'm getting different results on different machines/environments
There's a reason "they" don't often let me near build systems.....
Ok, splendid. I suggested removing things to see if it was a bad idea. It is. Almost.
So does it still make sense to remove the log4j jars in contrib in the 3_x branch?
I did as you suggested, and of course started getting "classNotFound" errors for JUnitTestRunner and so-on. So I included these lines in Solr's build.xml.
in place of java.class.path and all is well. Is this the path you'd go down? I'm not very comfortable having Solr reach over into Lucene, but what do I know?
It should be fairly obvious by now that I'm not very ant-sophisticated, is there a preferred way of doing this? Because if this is OK, it seems we should also remove junit-4.7.jar from ../solr/lib and point anything that needs it should path to ../lucene/lib as well.
I'm currently testing similar changes on the 3_x build with log4j files removed. But that worked before as well.....
Let me know