jar-dependencies icon indicating copy to clipboard operation
jar-dependencies copied to clipboard

Will not pull beta packages?

Open andrewvc opened this issue 9 years ago • 4 comments

Hi, I'm trying to setup jar bundler to work on my fork of the logstash elasticsearch output, and when I switched the maven deps from 1.7.1 to 2.0.0-beta1 it stopped working.

Now when I run bundle it just doesn't do anything and silently errors. Any ideas what's happening here?

/cc @purbon

andrewvc avatar Aug 28 '15 20:08 andrewvc

Is this an issue regarding ruby/rubygems using the dot vs the dash for pre releases? @mkristian do you think there is an "easy" fix for that in jar-dependencies world?

Thanks a lot,

  • purbon

purbon avatar Aug 28 '15 21:08 purbon

@mkristian @andrewvc more info on the difference, here there are:

  • maven format: https://docs.oracle.com/middleware/1212/core/MAVEN/maven_version.htm#MAVEN400
  • rubygems format: http://guides.rubygems.org/patterns/#prerelease-gems

purbon avatar Aug 28 '15 21:08 purbon

I am not getting the issue. a gem needs to follow rubygems version constraints. so 2.0.0-beta1 is not a gem version. and a version for any jar is maven can be more or less anything.

@andrewvc unfortunately I can not access your private fork or it is gone by now.

mkristian avatar Sep 03 '15 18:09 mkristian

assuming 1.7.1 is the version of elasticsearch.jar then switching to 2.0.0-beta1 on jar declaration of the gemspec is just maven under the hood. so indeed I found: http://search.maven.org/#artifactdetails|org.elasticsearch|elasticsearch|2.0.0-beta1|jar

@andrewvc could you provide me with the output of

JARS_DEBUG=true bundle install

and which version of jar-dependencies ?

mkristian avatar Sep 03 '15 18:09 mkristian