The JAR generated by the jenkins build server appears stale and not from master.
Fixed this in jenkins by adding "clean package" to the build directives, so that build in fact cleans before running.
We now have a release server http://ec2-54-243-59-213.compute-1.amazonaws.com/archiva/browse/org.apache.hadoop.fs.glusterfs/glusterfs-hadoop/ And the build now timestamps jars: http://ec2-54-243-59-213.compute-1.amazonaws.com:8080/job/glusterfs-hadoop/ws/target/ The timestamping will gaurantee that the build server jars are dated clearly, and the actual release server will provide us all with a single place to get our artifacts for testing and release.
We now have an internal build server jenkins-rhs.lab.eng.blr.redhat.com:8080 Which has the glusterfs-hadoop builds in it, and it is always non-stale. For releases: http://23.23.239.119/archiva/browse