: If the fact that javadocs fails because Oracle removed the
: package-list for java5 javadocs is a blocker,
:
: then on RC3 should i vote -1 because the tests often completely hang
: on java5 due to JVM concurrency bugs?
a) API Compatibility has nothing to do with which JVM you choose to try
and run tests on. If the Oracle Java5 JVM is buggy, you're welcome to use
any other Java 1.5 compatible JVM you want -- but it doesn't change the
fact that the 3x branch is documented to be Java 1.5 compatible. If you
want to beat that horse some more go ahead, but it really has nothing to
do with this dicussion.
b) For the sake of argument: I do in fact think there is a huge difference
between the following caveats:
1) "Some tests may fail, sometimes, depending on your JVM/Platform."
2) "Building javadocs is garunteed to fail (regardless of your JVM
implementation, JVM Version, or Platform) unless you override a
certain (undocumented) build property."
...if we're not going to care enough to respin an RC when the build.xml is
completley unusable (and we already have a patch to fix it!) then why
bother giving a crap if any of the code is usable? or if any tests pass?
I mean seriously ... WTF is the point of a release that we know is broken
for all users? the main reason we even have an RC2 is because one test
(in a contrib!) would fail on some OS's -- if that's worth making RC2 then
why the fuck isn't it worth making an RC3 when it's impossible to
generate documentation on any fucking machine in the world?
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
