Re: [Engine-devel] JDK Failures with .gwttar
On 07/23/2013 05:28 PM, Leonardo Bianconi wrote:
Hi Itamar!
After rebasing our patches against the master branch from the git
repository, we noticed that the current version of the oVirt engine uses
a new version of GWT. This introduced a problem while building the
engine, which is documented in this link:
“IBM JDK failures with .gwtar and compile” -
https://code.google.com/p/google-web-toolkit/issues/detail?id=7530
The problem here is that we are using a different JVM (the IBM’s one)
than the one that compiled the gwt files. In the beginning, we tried to
use the Open JDK, but it was too slow to be used, it takes about 1h20m
to build everything against 7m of IBM JDK, so we are using the IBM one.
We have a question, as we are working on oVirt to work with different
architectures, should we work on fixes when we find a problem like that?
For this issue we got a workaround, using an parameter on the build
command and removing the gwt cached files.
Hi Leonardo,
yes, we should strive to fix these things.
it would be even better if we can detect them earlier, by having a
jenkins ppc slave to the ovirt jenkins, or just a local jenkins by you
which will report when a patch breaks on ppc/ibm jdk for further
consideration).
questions:
1. is there a bug right now to fix? we need the build to know to add the
modifier when using ibm jdk.
2. (added alon) i remember we actually have an issue with ibm jdk wrt
certificates or something which is worth considering in this context.
3. do you have more details on the openjdk performance issue on ppc to
try and fix that one? can you open a bug on this and forward to us?
Thanks,
Itamar