XOM API for Processing XML with Java

["Steve Loughran" <steve.loughran AT gmail.com>]

On 16/11/06, Elliotte Harold <elharo AT metalab.unc.edu> wrote:
> XOM 1.0 is now in the Maven repository, and I've updated Jaxen (CVS
> version) to use it. That's probably all I'm going to do for now. I think
> overriding locally for other projects is probably the way to go.

thanks!

If you could point me at the URL to the jaxen pom file, I will give it
a quick review.

> Past Jaxen 1.1 (which I'm still hoping to get out this year) we probably
> will move Jaxen to Maven 2, and then we can use version ranges.

Makes sense. Ivy has a task to create POM files from Ivy ones but it
is undocumented, which implies untested/unstable. But Ivy does give
you dependency management without the inflexibiliy of Maven2.

> Would it be possible to produce and upload Maven 1 and Maven 2 POMs for
> the same Maven 1 project? or would they conflict with each other?

It should be ok. They only copy the maven1 poms into the M2 repository
if there is no m2 pom.

-steve