Found at http://www.xom.nu/ Note that I tried to install by cloning the xom-1.0-r2.ebuild, calling it xom-1.1.ebuild. The ebuild digest ran ok but I ran into errors during it's emerge, I suspect because it tried to do it's own (non-portage) build of jaxen.
Yeah I tried this too and found that the build.xml needs patching so that it does not try to checkout and build jaxen from CVS but instead use the system installed copy of jaxen. Sorry that you haven't gotten a any response to this bug so far.
This would look like an non obvious bump. I looked into it today. As Betelgeuse pointed out, it tries to checkout and build Jaxen. The problem is that Jaxen itself depends on XOM so we have a circular dependency there.
A little more inspection, and I think it would be doable, just would need to break jaxen into something like jaxen-core and jaxen-xom. Jaxen-core would need to be built before xom, then jaxen-xom could be built.
(In reply to comment #3) > A little more inspection, and I think it would be doable, just would need to > break jaxen into something like jaxen-core and jaxen-xom. Jaxen-core would need > to be built before xom, then jaxen-xom could be built. > Looks like a similar solution to what we have with jdom-jaxen.
Just a side-note: xom-1.2.1 is already available. I am curious if this bug gets attention at the moment (I need a newer xom at work). I am not very familar with ebuilds (esp. java eclasses) but I am willing to spend time on it. So it would be really nice, if some of you point me to some information on how to use these eclasses properly.
(In reply to comment #5) > but I am willing to spend time on it. Great to hear. Thanks for being interested. > So it > would be really nice, if some of you point me to some information on how to use > these eclasses properly. > You can read our wiki[1] and developer documentation[2] and follow the links in those. 1: http://overlays.gentoo.org/proj/java/ 2: http://www.gentoo.org/proj/en/java/java-devel.xml
xom's currently at version 1.2.6. It still seems to bundle a ton of stuff. If I get around to it I might try writing an ebuild for it.
Created attachment 262307 [details] xom-1.2.6 ebuild I made an ebuild for xom-1.2.6 and patched xom's build.xml to not use jarjar or any of the bundled jars.
Created attachment 262309 [details, diff] build.xml patch
Created attachment 262313 [details] xom-1.2.6 ebuild Remove junit dependency as tests aren't run
Created attachment 262315 [details, diff] build.xml patch
Created attachment 262319 [details] xom-1.2.6 ebuild Moved EAPI above JAVA_PKG_IUSE and changed src_prepare to java_prepare. I was just made aware of the circular dep on jaxen though.
We currently decided to keep the bundled sources because they're moved into XOM's own package hierarchy. I hopelessly filed an upstream bug. Let's see if they improve the situation somehow.
Tried the above ebuild of Kenneth and it compiled, but the following emerge of json-lib failed then.
Created attachment 263255 [details] json-lib failed emerge log
Created attachment 265251 [details] xom-1.2.6-r1.ebuild Alright, here's an attempt at an ebuild using the bundled jaxen sources.
Created attachment 265253 [details, diff] build.xml patch
(In reply to comment #16) > Created attachment 265251 [details] > xom-1.2.6-r1.ebuild > > Alright, here's an attempt at an ebuild using the bundled jaxen sources. Thank you for your hard work. I made a few more modifications to the ebuild and committed.
