-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on TravisCI with jruby 9.1.5.0 (2.3.1), works with jruby-1.7.25 #52
Comments
that is strange. hard to say. I it just the head of your repo I will need to dig into this. we had this problem before that something is activating jar-dependencies inside bundler (probably some rubygems code) and then there is this conflict. do you need jar-dependencies 0.3.9 ? because of the proxy stuff ? not sure if you really need it. next jruby-9k version will have 0.3.9 bundled. I am travelling the next two days, not sure if I find time over the weekend. so do not expect a fix this week |
Now worries, it actually works on my laptop with both versions of Ruby (using rvm) no problem. I'm just not sure why it's not working on TCI. Also, I do not check in the Gemfile.lock. It is a Logstash plugin and the plugin installs properly and works, but I'm curious now since I cannot seem to figure it out. Please let me know if you need anything else when you get to this. |
I am getting the same error on GitLab CI
This error occurs when CI executes this
This error goes away if I set the version of Anything else I can try out to better debug ? no idea what's going on, actually Using jruby v9.1.6.0 |
question: is this q rvm based build ? do you rvm locally ? really hard to debug |
@mkristian I use rbenv locally. |
@detj thanks, I try rvm - maybe I can reproduce it. any particular reason to use jbundler over jar-dependencies ? jar-dependencies comes with do you need to vendor the jars during build ? they just get copied to some other locations. |
@mkristian So, I need a few Jars from a maven repository. I also have a |
@detj lock_jars will produce a Jars.lock but the Jarfile is the same. I doubt (judging from afar) that you need to vendor your jars for the tests. btw jbundler uses jars-dependencies so does |
@mkristian yes, correct. need to vendor the jars for the tests. |
@mkristian Here is a portion of my ice_nine (0.11.2)
jar-dependencies (0.3.11)
jbundler (0.9.3)
bundler (~> 1.5)
jar-dependencies (~> 0.3)
maven-tools (~> 1.1)
ruby-maven (~> 3.3, >= 3.3.8)
jdbc-postgres (9.4.1206) I'm using jruby 9.1.6.0 and |
we're seeing this also in logstash in many places (e.g. https://travis-ci.org/logstash-plugins/logstash-patterns-core/jobs/265018856#L440-L451) , the easiest way to reproduce is:
|
@jsvd since I am basically offline until end of August - I can not have a look. |
I'm getting an error on TravisCI with jruby 1.7.25, but jruby:
Gem::LoadError: You have already activated jar-dependencies 0.3.5, but your Gemfile requires jar-dependencies 0.3.9. Prepending
bundle execto your command may solve this.
I have this in my gemfile:
gem "jar-dependencies", "~> 0.3.9"
Here's the output from the working one:
https://travis-ci.org/mikebski/logstash-filter-collect/jobs/190958310
Here's the non-working one:
https://travis-ci.org/mikebski/logstash-filter-collect/jobs/190958311
Any ideas?
The text was updated successfully, but these errors were encountered: