That's pretty much what I thought. Perhaps we can start a discussion at some
point about improving the way that the automated tests are conducted to provide
more "throughput".
As for the second kind of testing, could this be provided without more burden
on the committers if more people/institut
I think the automated tests would need to remain limited to the
recommended JVM- I wouldn't be able to bear an hour and a half wait
for the sanity builds. That said, it would be great if we could test
OpenJDK in the way that we test different RDBMS and OS configurations
before releases.
On 7/27/1
It has to be noted that an additional JVM/JRE could almost double the amount of
testing to be done. Fedora testing (as will testify those who are slogging
through it for 3.5 even as we speak) is somewhat burdensome.
Can Fedora's current testing machinery (including the human resources that
pow
+1 for openjdk
On 27 Jul 2011, at 1:37 PM, aj...@virginia.edu wrote:
> OpenJDK is one with which I've had no problems running Fedora, at least on
> Linux. Some of the others were mixtures of Apache Harmony with other VMs. A
> few of them worked well, others... not so much. {grin} Fedora, in fac
OpenJDK is one with which I've had no problems running Fedora, at least on
Linux. Some of the others were mixtures of Apache Harmony with other VMs. A few
of them worked well, others... not so much. {grin} Fedora, in fact, became
something of an acid test for me looking at alternatives to the Or
I suspect the extra PermGen space is being taken up by autogenerated
classes. Depending on how the soap interface is constructed, there are a
number of classes that are not generated until you actually call a soap
method. These MIGHT only live in the session, and thus be discarded and
autogener
