replace version ranges with lockdown version

maven is reproducible when there are not version ranges in play. these artifact with version ranges I see anytime I am using the jruby maven artifact since maven tries to take the latest version today. so any new version might break my project because it was tested against another version. basically the drama of time before bundler.
Fixed Guava #1505: NoClassDefFoundError loading Finalizer$ShutDown under unusual class loading conditions.
https://code.google.com/p/guava-libraries/issues/detail?id=1505
Simplify Delegate handling
Add array-of-struct test
Add nexus-staging-maven-plugin
[maven-release-plugin] prepare release 1.0.5
[maven-release-plugin] prepare for next development iteration
Update release tag format
Add deploy goal to release plugin
[maven-release-plugin] prepare release 1.0.5
[maven-release-plugin] prepare release 1.0.5
Do not push changes during release
Roll back version
Remove deploy goal from release
[maven-release-plugin] prepare release 1.0.5
[maven-release-plugin] prepare for next development iteration
Disable broken sonatype plugin
Reset to 1.0.5-SNAPSHOT
Re-enable push-on-release
[maven-release-plugin] prepare release 1.0.5