Upgrade cobertura and findbugs plugins

Hmm, those version don't seem to work but the old ones do:

Trying to get missing dependencies (and updated snapshots) required by jaxen:

• Attempting to download maven-plugins:maven-cobertura-plugin:2.5.1:plugin from http://repo1.maven.org/maven
• Attempting to download maven-plugins:maven-cobertura-plugin:2.5.1:plugin from http://dist.codehaus.org/
• Attempting to download maven-plugins:maven-findbugs-plugin:2.4.0:plugin from http://repo1.maven.org/maven
• Attempting to download maven-plugins:maven-findbugs-plugin:2.4.0:plugin from http://dist.codehaus.org/
  -------------------------------------------------------------------------------
  >> The build cannot continue because of the following unsatisfied dependencies:
• maven-plugins:maven-cobertura-plugin:2.5.1:plugin
• maven-plugins:maven-findbugs-plugin:2.4.0:plugin

The plugins shouldn't be listed as dependencies, but should rather be listed as plugins. I don't know where the pom.xml that's in the central maven repository came from as I don't see it in SVN, but the pom.xml that's attached to http://jira.codehaus.org/browse/JAXEN-149 is far better. Can we replace the version in the maven repo with that one?

I can make edits to the project.xml (we do not have a pom.xml) checked into our SVN repository. I have no ability to push anything into the central maven repository, nor do I know anyone associated with this project who can. The last time I tried to do that, it wasted many hours of development time to absolutely no effect.

I see. It would still be nice to get the pom.xml checked into svn that way the next time whoever it is that deploys to the Maven Central Repository does it they use an updated version of the file. You do have a pom.xml - it's just not checked into svn. Look at the Maven Central Repo: http://search.maven.org/#browse%7C1190549344. It would be very nice to have this file version controlled that way there's some way of making improvements for the next time a version of the file is pushed. I've attached a pom.xml that you can use.

To clarify, see jaxen-1.1.3.pom in the Maven Central Repo (http://search.maven.org/#browse%7C1190549344). The file isn't actually named pom.xml there, but the file contents are the same. If you want to name it jaxen-1.1.4.pom instead of pom.xml when you check it into SVN that would be fine too.

Thanks. This one seems to work so I'm going to go ahead and check it in as pom.xml. I did make one change. The version number is now 1.1.5. Compile and test both work. Dist seems not be recognized? Maybe the name has changed in maven 3?

It does have one problem I noticed with the site target:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project jaxen: failed to get report for org.codehaus.mojo:findbugs-maven-plugin: Unable to parse configuration of mojo org.codehaus.mojo:findbugs-maven-plugin:2.1:findbugs for parameter localRepository: Abstract class or interface 'org.apache.maven.artifact.repository.DefaultArtifactRepository' cannot be instantiated -> [Help 1]
[ERROR]

We'll also need to update the build instructions.

Moving forward if this works out we can delete the old project.xml, but for the moment I'm going to hang onto it at least until we work out these remaining issues.

If someone wants to figure out how to push it to the central maven repository, feel free.

The site target has a couple of these warnings:

[WARNING] Using platform encoding (MacRoman actually) to copy filtered resources, i.e. build is platform dependent!

Any ideas how to fix them?

Got it. I should google before posting.

<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
</properties>

I've upgraded the plugins to the suggested versions. We should consolidate and track further maven 3 work under Jaxen-149.

Great! Thanks so much Elliotte. I've attached a few more tweaks to the file (generated this patch by running "svn diff"). "mvn javadoc:javadoc" was broken because links was improperly specified, a few formatting issues, and a few dependencies that should have been specified as optional. Otherwise, it looks really great to me!

Thanks. Patch applied. optional dependencies look cool. This should help control our notorious dependency problem.

Cool, thanks Elliotte! I've got one more patch for you. This one generates source and javadoc jars, which will be needed for whenever the next push to Maven happens.

Now if we can just figure out who has permission to push a new version to the central Maven repo I'd be happy to do it if you're able to give my account access. I pushed a few of the Google libraries back in the day, so I'm somewhat familiar with the process. You can login to the management console at https://oss.sonatype.org/index.html#welcome My username is bmccann

Actually, scratch that last patch. This one is better. It uses the Maven repository plugin to create a bundle jar that you can upload to the Sonatype Nexus. You just need to run "mvn source:jar javadoc:jar repository:bundle-create"

Ok, this is the last one This v2 of the patch signs the artifacts created by the repository bundle plugin, which will be necessary to upload to Maven central. You still use the same command mentioned in the last comment ("mvn source:jar javadoc:jar repository:bundle-create"), but will need to create a gpg key first (see http://www.benmccann.com/dev-blog/creating-asc-signature-files-with-gpg/). I uploaded the bundle to a staging maven repo to prove it works.

Hey Elliotte, saw that you applied the patch, so I just wanted to say thanks!