Skip to Content.
Sympa Menu

xom-interest - [XOM-interest] XOM status

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: Elliotte Harold <elharo AT metalab.unc.edu>
  • To: xom-interest <xom-interest AT lists.ibiblio.org>
  • Subject: [XOM-interest] XOM status
  • Date: Fri, 07 Jul 2006 07:43:00 -0400

Just a quick note to keep people abreast of what's happening.

At this point, I feel like XOM 1.2 is pretty much done code wise. I don't foresee any other bug fixes, optimizations, or new methods. This will actually be a fairly minor release compared to 1.1. Yes, there are still optimizations I need to investigate and implement; but I don't want to hold up 1.2 while I do that. Since they're not externally visible, additional optimizations can always be done in a 1.2.1.

I am, however, a little blocked by Jaxen. As you may or may not know the Codehaus servers that host Jaxen crashed majorly a couple of months ago. backups were not up to date. That's all been recovered from by now and no Jaxen work was lost. However as a result of that CVS access to Jaxen has been disabled. What we have now non-anonymous Subversion access.

XOM's Ant build file actually tries to check the latest Jaxen code straight out of CVS. This now fails. For those of you who watch Gump, this is why Gump is failing XOM daily.

What I need to do is make a JAR of the relevant Jaxen code just for use with XOM, and check that into XOM's own CVS. None of this will affect the end product, just the build process. This is probably a good thing, on its own. Even if Jaxen CVS were working, the way XOM was built was a little flaky. Changes in Jaxen could change XOM from day to day even if nothing else had changed.

Ideally I'd like to be able to build XOM 1.2 against an official release of Jaxen, specifically 1.1. That makes it easier to track bugs and build the whole package. Fortunately, Jaxen 1.1 is very close. I and several other people have now closed all but one of the known remaining issues before Jaxen 1.1 can be released. The last issue is just documentation, and if nobody fixes it soon; I may argue for releasing 1.1 anyway.

Once that's done, I can push out the usual beta-->RC-->final releases of 1.2.

--
Elliotte Rusty Harold elharo AT metalab.unc.edu
Java I/O 2nd Edition Just Published!
http://www.cafeaulait.org/books/javaio2/
http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/




Archive powered by MHonArc 2.6.24.

Top of Page