incorrect maven 2 poms on ibiblio are not from cvs

http://www.ibiblio.org/maven/jaxen/poms/ looks like Maven 1 poms to me. I'm not sure what you're loking at. I don't know anything about maven 2 POMs for jaxen.

Also Gregory Block is wrong about jaxen's structure. There are no plugins. There's one monolithic code base that depends on everything. Breaking this up into a more modular system has been on the todo list for a while now, but I doubt we'll get to it in time for Jaxen 1.1.

What he's referring to is that in maven 2 you can define some dependencies as being build-time only (that's what 'scope' is for) so that you don't pull them in as transitive dependencies when you're only depending on jaxen. It isn't about splitting jaxen into modules, just recording in the pom that not everything is required to use jaxen at runtime.

Now compare our project xml:
http://cvs.jaxen.codehaus.org/viewrep/jaxen/jaxen/project.xml?r=1.58

with what's up on ibiblio, eg:
http://www.ibiblio.org/maven/jaxen/poms/jaxen-1.1-beta-4.pom

The one on ibiblio begins with '<modelVersion>4.0.0</modelVersion>'.
take a look at 'modelVersion' - not only is the modelVersion element just called 'version' in maven 1, the value refers to the maven 2 schema. All of the pom files there are for maven 2.

I've changed the title to make it clearer what the problem is here Elliotte. I know we dont have m2 poms, but they've sprouted up on ibiblio, and don't seem connected with Peter deploying the corresponding jars.

I'm guessing one of the maven people has added them to support the m2 release, and its ended up with complaints about jaxen. I'd prefer we had /no/ poms on ibiblio than have random files appearing there unconnected to our releases; who should users complain to?

When I asked if we could fix this without upgrading to m2, I was referring to the method of deployment onto ibiblio (ie maven jar:deploy). Since we use maven 1, its hardly going to deploy maven 2 descriptors for us.

I'm not sure what's happening there. I guess some maven person went through and modified the poms, possibly automatically. We shoudl probably file a bug on this with maven and ask for our orignal poms back or something.

I know the maven guys have a routine that auto-generates m2 poms from m1 project.xml's....

And speaking of m2, I took a look at converting the build to m2 this past weekend but gave up. There's too little documentation, especially on migrating, given that we have extra things in our build like cobertura and findbugs. If anything, going back to just an ant build seems most sensible.

Basically what happened here:

• m1 poms get automatically converted to m2 poms in /maven2/
• We changed /maven/ to map to /maven2/ to ease long term maintenance.
• This means m1 poms aren't accessible from ibiblio any more. This shouldn't be a problem, as m1 doesn't use them.

If this is causing an issue, or the conversion is wrong, let me know (you can file a bug at MEV under jira.codehaus.org). If it just looks different but appears to be correct in terms of data, everything should be fine.

In terms of what I can see here, you want to change the way it is converted - this can be done in m1 by adding:
<properties>
<optional>true</optional>
</properties>

(or <properties><scope>test</scope>, or similar...). These have no effect on m1, but will be converted to m2 correctly.

BTW, Peter - let me know if I can help regarding converting to m2. There is admittedly little documentation on converting from m1 because there isn't a great migration path, but it is meant to be easy enough to start from scratch (in parallel to the existing build) without being any more time consuming than a migration, or an ant build. Some folks are working on organizing the documentation at the moment in the wiki.

Brett, thanks for the offer of m2 conversion help – I might hit you up on IRC about that when I get some free time to devote to it.

If you're going to discuss this on irc, can you ping me? Adding a comment to this bug would do, I'll pop over if/when the mail comes in. If I'm not around, just don't wait for me. I'm just interested in listening in on this. Thanks!

I'm not convinced this is our bug. It really sound slike it's Maven that has the problem. Jaxen itself is just fine. If there's a specific action Jaxen can take short of moving to Maven 2, and the Maven folks tell us what that is, then we can do it.

Longer term I think we'll move to Maven 2 after 1.1; and presumably that will fix any remaining issues.

Well, since this doesn't seem to have happened yet, is there any interest in having an outsider do a Maven 2 conversion for you? I might be persuadable (although I'd have to check out XOM to get a sense for what's required) before I make any commitments.

Geoffrey,

Now would be a good time to do a Maven 2 conversion since the code's fairly stable and no other major work is happening at the moment. Possibly we could release a 1.1.3 that did nothing except upgrade to Maven 2.