Maven POM includes maven plugin dependencies that should probably be test scope

This doesn't seem to be an option in maven 1.1:

~/Projects/workspace/jaxen$ /opt/java/maven-1.1/bin/maven dist
__ __

-------------------------------------------------------------------------------
>> Error parsing project.xml '/Volumes/Macintosh HD/Users/elharo/Projects/workspace/jaxen/project.xml'
>> ParseError at [row,col]:[306,14]
Message: Unrecognised tag: 'scope'
-------------------------------------------------------------------------------
BUILD FAILED
-------------------------------------------------------------------------------
Total time : 0 seconds
Finished at : Saturday, May 5, 2012 1:52:35 PM EDT
Final Memory : 1M/81M
--------------------------

I see that Jaxen actually builds with Ant and generates the POM file. Does this generated POM file need to support 1.1? I'm not sure about the 2.0 branch but 'scope' is supported at least in 2.2 and 3.0. The Maven site does not even link to version 1.1 anymore.

I don't think so. At least I don't see any build.xml in my local copy, and I've been using maven to build it.

What you're describing sounds more like how XOM builds.

Yes, my mistake.

The project.xml file defines POM version 3. POM version 4 supports the 'scope' tag.

If you want I can rewrite the POM in version 4 for you.

If you send a patch (with appropriate license verbiage) I'll be happy to plug it in and see if it works.

Do be warned that my patience for spending time debugging maven issues is essentially nil. I've wasted way too many hours on fruitless efforts to satisfy the beast that maven has become, so it pretty much needs to work out of the box with the current codehaus infrastructure.

Can I assume that the Codehaus infrastructure has Maven 2 or 3 binaries?

I don't know. You'd have to ask a codehaus administrator or some such.

Some questions:

1) What source level should the code be compiled at?
2) Are the source files UTF8-encoded?

Just for your information, the src folder is not correctly organized according to http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html. Someone seems to have misread it and created src/java/main og src/java/test instead of src/main/java and src/test/java. This is easily configurable in 2.0+ as it was in 1.1, though, so it's necessary to fix though I believe it to be prudent.

I have been successful in creating an equivalent Maven3 POM.xml. It requires the following conditions/actions to be taken.

1) Verify that the build server can run Maven3 (for the POM file).
2) Verify that the build server can build with JDK5 (for the newer version of the findbugs plugin).
3) Introduce the new POM.xml.
4) Correct file structure to be in line with the Maven SDL.
5) Introduce site.xml descriptor (which now includes navigation).
6) Delete site/xdoc/navigation.xml.

It's a bit of work, I know, but let me know if you're still interested.

Maven3 compatible POM

Site descriptor for the maven-site-plugin. It replaces the navigation xdoc file.

sounds plausible if it all works, though I may push 1.1.4 first so other bug fixes don't get blocked on this.

I would avoid assuming the files are UTYF-8 encoded. Try to keep things to ASCII for now.

We compile with source level 1.3 and set the binary for 1.2.

I don't have any problem requiring the build to use Java 5 or later, provided the binaries are fully compatible with 1.2.

Maven3 compatible POM file. Now with correct target (1.2), source (1.3) levels and assumption of source files being UTF8 encoded.

I read your comment wrong. No matter, just exchange UTF8 for ASCII in the POM.

For reference, the steps involved in correcting the file structure are:

• Delete 'xdocs/navigation.xml'.
• Rename 'xdocs' folder to 'src/site/xdoc'.
• Create 'src/site/site.xml'.
• Create 'pom.xml'.
• Rename 'src/java/main' to 'src/main/java'.
• Rename 'src/java/test' to 'src/test/java'.

I seem to have missed the project.properties file. I will attempt to incorporate the information contained within and upload a new POM.

Some more steps.

• Rename 'src/site/xdoc/stylesheets' to 'src/site/resources/css'. Rename the stylesheet you actually wish to use for the site to 'site.css'.
• Create checkstyle.properties.

Includes the checkstyle properties from project.properties.

Updated POM.

This has now been fixed in pom.xml. (project.xml will go away once all issues with pom.xml are resolved.) We should consolidate and track further Maven 3 work under Jaxen-149.