Comment 61 for bug 305790

Matthias,

I discussed this issue with Martin and he thought you might be able to resolve these two problems?

I do not know enough about Java to determine how to safely backport the changes needed for jaxme and updating to the subversion release seems to not be a good idea due not knowing if it is reliable also it switches to maven which brings in many more packages from universe.

The xom issue appears to be either something related to the buildd or something else causing the level of resources to increase such that it can't compile on the buildd. I am not sure what is happening here as it compiles fine on my local machine and the previous person who uploaded it had it compile fine for them as well. Perhaps some configuration file needs to be tweaked? I remember that something like that needed to be done in the past for gcj native compiles for OOo, but my memory may be faulty.

Chris