: But I'm just pointing out that with "bugs" like the javadocs thing, : its not really a lucene bug. Likely its a transient issue with : oracle's configuration... does that mean all of our past releases are : broken too???? Because, ant javadocs won't work there either.
Those releases are already out there, we can't change them, and if someone asks "how come the build for 3.4 fails?" we can explain. But shipping 3.5, knowing that everyone who tries to build it is going to get a failure the minute it goes live, seems idiotic. : I did a quick google search: "http://java.sun.com/j2se/1.5/docs/api/"; build.xml ... : Are all of their build files "completely unusable". Should the java Probably not, because I sincerly doubt those build.xml files jump through all the hoops we jump through to fail hard on any javadoc warning. (Remember: "fail on warning" is not a feature of javadoc, or the <javadoc/> nat target -- it's something special we do in our build.xml. It's sometihng that in general i think is a very good idea, and i don't suggest we change it, but it's the reason why we shouldn't just say "it's oracles problem" when javadoc spits out a warning because the URL is down) So let's just fucking fix it once an for all, so we'll never-ever have to care if Oracle screws up the package-list yet again, and so the 3.5 build will actually *work* -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
