I'm working with WSF here: http://wso2.org/project/wsf/ruby/1.1.0/docs/manual.html
The documentation cites 1.8.5 or above, but I'm running into issues with 1.9.3p0. Can anyone confirm that this framework is incompatible with ruby 1.9.3?
The WSF/Ruby framework can most probably be incompatible with 1.9.3p0. That statement of version 1.8.5 or higher is based on the assumption that WSF/Ruby will remain backward compatible. Since there is no active development on the project, any issues with later Ruby versions may not be fixed.
Related
I cloned one of my 3years old project from Github to resurrect, however I'm getting bunch of migrations, gem, etc errors. Googling gives me tips about possibly using wrong ruby version.
I want to assign the specific rbenv local rubyver but I don't know which one I used and I can't find it in any settings?
Any idea how I can find what Ruby version is this project using?
There's a few places this might be annotated:
A .ruby-version file, though these are often ignored to avoid friction between developers with slightly different versions. This is what rbenv uses, as well as other tools like RVM.
The Gemfile can have a ruby version lock in it, though this is usually a minimum requirement, like >= 2.3.0.
The README if the developer is kind.
Otherwise, there's no real way to know.
It's worth noting that Ruby 2.0, 2.4 and 3.0 are often the biggest upgrade hurdles, so it's worth trying with the latest version you can get away with, like 2.7.2 if practical, 3.0.0 if possible.
I am learning to use opencv. I am trying to install it from opencv official website. Is it okay to install the latest version(4.0.0)? I suppose that latest version should be compatible with the earlier versions so there shouldn't be any problem.
Is it okay to install the latest version(4.0.0)
Generally: Yes, why not? If you want to use the newest modules (like gapi, added in 4.0.0) you will need to use the newest version. It also makes a lot of sense to use the newest because they improved the performance for some operations compared to version 3.x.x.
I suppose that latest version should be compatible with the earlier versions so there shouldn't be any problem
Not necessarily. Version 4 to 3 might be compatible (I'm still using 3.x.x), but 3 to 2 are in fact not completely compatible. Most noticeable they moved a lot of functionality from the highgui package. From the official change log:
Although OpenCV 3 can be viewed as refined OpenCV 2 and is similar to the latter, this new version is not completely backward-compatible with OpenCV 2
I'd recommend you to read the official changelog for yourself and decide if you need the new functionality or if you want to stay with an older version. If you are new to OpenCV it probably makes sense to start with the newest version.
I'm trying to use iZ3 to generate the interpolants. However, there is no iZ3 binary after installing Z3, and can't find any information about how to install it.
Thanks!
iZ3 is not available in the latest version. The Z3 4.1 is the last version that includes iZ3.
This version can be found here: http://research.microsoft.com/en-us/um/redmond/projects/z3/older_z3.html.
Keep in mind that iZ3 depends on software components that are not owned by Microsoft, and could not be released with the rest of the source code at http://z3.codeplex.com.
What is the latest stable version of rails? I want to install rails 3.1 but I see there is 3.1.3 now, what is the difference? What ruby version is it most compatible with?
I recommend to always check on GitHub via the "branches" menu what the latest version is on each branch.
You can see the latest version easily by checking the contents of the RAILS_VERSION file
https://github.com/rails/rails
You could also check RubyOnRails.org, but looking at the source code is the most reliable way.
If you already have a Rails App in production, I would highly recommend: don't just blindly take the latest version just because it just came out -- there were many cases in the past where a new version introduced incompatibilities or new bugs which were serious enough to have to wait for a fix before the features in the Rails release were really usable. I know a couple of people who have Production sites and still run 3.0.11 or lower, rather than 3.l.x
Again: check on GitHub under "Issues" which open Issues there are for a release, and/or google "Rails 3.y.z Problems" with the exact version number, so you get a feel of what problems could be introduced by upgrading to a new / the latest version.
On Wikipedia they have a list of historic release dates for the major Rails versions:
https://en.wikipedia.org/wiki/Ruby_on_Rails
The Rails version numbers have been explained reasonably well (Joseph Le Brech's answer), but the Ruby version numbers are slightly confusing and I could see why it's not really obvious what's going on there.
Joseph's explanation of Rails version number scheme is correct for Rails, but Ruby has a slightly different approach
1.9.3 is the most recent version of Ruby. Having said that, it was only released maybe a month ago, so it's possible there are breaking issues with certain gems. (Yes, there were breakages. Ruby in general will introduce breaking things between hotfix releases, and it's true here too)
1.9.2 is a more tried and true version of Ruby, having been out for at least 6 months now.
1.8.7 is the last version in the Ruby 1.8 line. Major language rework happened between 1.8 and 1.9, so some older gems may not have made the transition.
My recommendation: use Ruby 1.9.2 and Rails 3.1.3, unless you have really good excuses not to.
Ruby 1.9.2 is probably the safest bet for a Rails newbie, or green-field projects (projects without a lot of preexisting code). Rails 3.1 is an excellent version of Rails, which solves a lot of problems I had with the framework.
Rails 3.1 was released this fall, so old tutorials won't work, or will give odd errors. Try to look and read what version of Rails the book/tutorial/website/blog entry is talking about, before you dive in.
Latest stable release is always shown on the Ruby on Rails website's home page here http://rubyonrails.org/
To list all rails versions by gem:
gem list -ra rails | grep -G "^rails\ "
It's also helpful for cheeking what is the latest version for 4.x, 3.x and 2.x too.
According to rubygems, it's 3.1.3. Looks like you forgot a ..
major.minor.hotfix hotfixes will never change the behavior of an app unless you previously had a workaround for a bug implemented. Apps can easily be upgraded thru minor revisions, but it's usually not worth it and can be a distraction from getting features out of the way.
The latest release is 3.1.3. This is a minor release which has security and minor improvements.
The main version is 3.1, while minor upgrades are included in 3.1.x releases.
Anyway you should always use the latest one.
usually if you'll pull the latest rails gem, it's the stable one (unless once in history). although you can still use ruby 1.8.x version with the latest rails 3.x, it is more recommended to use 1.9.x.
anyway, everything you might need is in http://guides.rubyonrails.org and some nice people (including myself) are answering all bunch of questions in IRC on irc.freenode.net (#rubyonrails and #railsbridge)
good luck
The latest release is 6.0. it was released on August 16, 2019, making Webpack default, adding mailbox routing. Rails 5.2 is still maintained.
I have vanilla Mac OS X Leopard which comes with 1.8.6.
I am new to RoR so will be following tutorials on the net. Am I likely to find problems following them when using later versions of Ruby?
I am currently looking at this one which mentions 1.8.6 and 1.8.7 - http://www.railstutorial.org/book
RoR tutorials will be fine on both, but if you're learning Ruby you should learn 1.9. 1.8.6 won't be supported in Rails 3, so I'd say go 1.8.7 or 1.9. I also recommend RVM for switching between Ruby versions.
The 1.8.x series (mostly 1.8.6) is still very much in widespread use and likely to remain that way for at least a year or so; 1.9 is slowly being transitioned to. Although there are some major differences between the two, for the most part everything you can do in 1.8 you can also do in 1.9.
Many of the trickier bits, like blocks and lambdas, get a bit of a makeover, but otherwise tutorials for 1.8 will still apply to 1.9 for the most part. You're likely to run into issues if you use gems and libraries from 1.8 in 1.9, however.
I believe Rails 2.3.5 is fully compatible with Ruby 1.9. The problem is not usually of Rails itself, but from other gems and plugins that might be outdated. However again try it, most likely you won't face problems.
Anyway, I highly recommend Ruby Version Manager(RVM) for trying several versions of Ruby.
I'll second the 1.9 recommendation. I'm kicking myself for not settling on 1.9 a year ago.
It's much more future-proof at this point. Targetting 1.8 is about like targeting Windows Vista at this point.