-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
rvm install of jruby fails with missing mvnw file #4793
Comments
@enebo could this be of the rescued tarball is missing the mvnw ? |
@mkristian yeah I missed this one...my script did not iterate over these last point releases...Adding now. |
This has been restored and works for me now. |
Thanks @enebo & @mkristian . After posting this issue, I switched to |
@enebo @mkristian Can you check to make sure that you added the missing mvnw? Because I am getting the same exact issue that was previously reported with jruby-1.17.16.1 Here is my output: M48619JHARDFOR:ruby jhandfor$ rvm install jruby-1.7.16.1
|
@jhandford which version are you seeing this problem with both 9.1.17.0 and 9.2.0.0 both seem to have a mvnw file? |
@enebo Below is my RVM Version. I am just running: rvm install jruby-1.7.16.1 I know that jruby-1.7.27 works fine. However, my code set needs jruby-1.7.16.1/ Ruby 1.9.3 installed. |
@jhandford oh I know what is up. Unfortunately, our S3 bucket was deleted again. The restoration does not include -src for 1.7.16.1 (and we don't have it). Also updated RVM know looks at maven instead of S3 (I don't know if this is for all versions of all versions later than 1.7.26. One of those two are your issue perhaps? You can still download -bin dist of 1.7.16.1 at: https://s3.amazonaws.com/jruby.org/downloads/1.7.16.1/jruby-bin-1.7.16.1.tar.gz |
Ahh thats it. Because I was like... rvm install jruby-1.7.16.1 was working 1 month ago. I hate that i removed it from my laptop. I am not familiar with getting jruby installed from the bin dist. Do I just un-tar the file in my .rvm/rubies directory? Or is there more steps that I need to do? Here is where I have jruby-1.7.27 installed at: M48619JHARDFOR:rubies jhandfor$ pwd |
@jhandford Yeah the tar can be unpacked into the rubies directory and you should be in business. |
@enebo Ok, I did that.... But I am assuming that there are some other steps that i need to do. M48619JHARDFOR:rubies jhandfor$ ls -ltr |
@jhandford I only have ~/rvm/gemsets/jruby/global.gems which contains:
I also notice I have ~/.rvm/gems/jruby-1.7.16.1@global -> /home/enebo/.rvm/rubies/jruby-1.7.16.1/lib/ruby/gems/shared. There is also a ~/.rvm/gems/jruby-1.7.16.1 which seems to almost have nothing in it (empty dirs) except for a wrappers directory which seems to have all the ./bin/* launcher scripts. Not sure if this is needed. I really thought unpacking would be enough. Sorry for the inconvenience :( |
@enebo Looks like I cant just untar the file and use with rvm. My /Users/jhandfor/.rvm/gems directory doesnt have any reference to jruby-1.7.16.1 I am assuming that there is no way that you could just recreate your S3 bucket with the src so that I can just run rvm install jruby-1.7.16.1? :) For now, I will try to manually point and create directories to reference the -bin distr files. Any other suggestions, in case this doesnt work? |
Hi All, I am not an expert in using or setting up Jruby, just following a copy of the
rvm_io.rvm1-ruby
ansible role. The details of the issue I am facing are as follows:Environment
Provide at least:
jruby-1.7.16.1
1.29.2
(tried with1.29.3
same result)Linux jenkins 3.10.0-327.36.3.el7.x86_64 #1 SMP Mon Oct 24 16:09:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Expected Behavior
Running
rvm install jruby-1.7.16.1 --auto-dotfiles --with-gems=bundler
I expect jruby to be installed without any errors.Actual Behavior
contents of the /var/lib/jenkins/rvm/log/1505984296_jruby-1.7.16.1/mvnw.log file:
As far as I know the same version used to work fine and have not changed anything since to cause this. I just downgraded rvm version to make sure it was not RVM causing the issue.
Happy to raise this issue against rvm.io repo if here is not appropriate
any insight would be much appreciated.
The text was updated successfully, but these errors were encountered: