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.
Merge pull request #4 from mkristian/patch-2

replace version ranges with lockdown version