[XOM-interest] 1.2.4?

[Elliotte Rusty Harold]

Has anyone tried 1.2.4 yet? Can I go ahead and release? Anybody find
any major bugs? Anyone who wants a more recent version of XOM in
maven, should really check this version out. 1.2.3 went out with a
major bug in its project.xml that wasn't caught until I tried to get
put into the main repository. XOM doesn't use maven itself, so if no
one steps forward to test it it's unlikely to get updated in a timely
fashion.

[Aleksander Adamowski]

On Fri, Dec 4, 2009 at 2:24 AM, Elliotte Rusty Harold

Post by Elliotte Rusty Harold
Has anyone tried 1.2.4 yet? Can I go ahead and release? Anybody find
any major bugs? Anyone who wants a more recent version of XOM in
maven, should really check this version out. 1.2.3 went out with a
major bug in its project.xml that wasn't caught until I tried to get
put into the main repository. XOM doesn't use maven itself, so if no
one steps forward to test it it's unlikely to get updated in a timely
fashion.

I don't know about others, but I don't have any installation of Maven
1 left to make a quick build... Everybody's moved to Maven 2 a long
time ago.

[Elliotte Rusty Harold]

Post by Aleksander Adamowski
I don't know about others, but I don't have any installation of Maven
1 left to make a quick build... Everybody's moved to Maven 2 a long
time ago.

Is Maven 2 incompatible with maven 1?

Jaxen's stil using Maven 1, which makes moving problematic unless
Maven 1 can use Maven 2 POMs. I could probably upgrade Jaxen, or
perhaps release parallel M1 and M2 POMs.

[Aleksander Adamowski]

On Fri, Dec 4, 2009 at 1:05 PM, Elliotte Rusty Harold

Post by Elliotte Rusty Harold
Is Maven 2 incompatible with maven 1?
Jaxen's stil using Maven 1, which makes moving problematic unless
Maven 1 can use Maven 2 POMs. I could probably upgrade Jaxen, or
perhaps release parallel M1 and M2 POMs.

I don't think Maven 1 project can use a Maven 2 artifact as a dependency, but:

1) We've already basically solved the upgrade of Jaxen to Maven 2 -
see http://jira.codehaus.org/browse/JAXEN-149
2) A Maven 1 project can be semi-automatically convertod to a Maven 2
project, so it shouldn't be hard for XOM - again, see JAXEN-149
3) I opt for a coordinated switchover to Maven 2 and release of Jaxen
and XOM. As to their dependencies, I think you'd have to look hard for
other projects that are still stuck at Maven 1.