[
http://jira.openqa.org/browse/WTR-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19923#action_19923
]
Jarmo Pertman commented on WTR-458:
-----------------------------------
I still don't see much of a point having that as a constant. As Ethan pointed
out then you can do it with Rubygems and it's nothing hard to do either!
Gem.loaded_specs["watir"].version.to_s # => "1.6.6"
Do we still need the constant itself?
I deleted it purposefully at the time, but can add it back if it's
really-really-really needed.
Working around bugs could be also done with Rubygems with "gem 'gem',
'=version'" instead of using some if-statements to read some values of some
constants.
> Watir version 1.6.6 doesn't show correct version number
> -------------------------------------------------------
>
> Key: WTR-458
> URL: http://jira.openqa.org/browse/WTR-458
> Project: Watir
> Issue Type: Bug
> Components: Gem installer
> Affects Versions: 1.6.6
> Environment: Windows XP, IE8
> Reporter: Ning Cao
> Priority: Major
>
> I'm running Watir on Windows XP and just updated to version 1.6.6, after the
> installation I wanted to check the version by using
> ruby -e 'require "watir"; puts Watir::IE::VERSION'
> [expected]Should show version number 1.6.6
> [actual]The output was:
> -e:1: warning: toplevel constant VERSION referenced by Watir::IE::VERSION
> 1.8.6
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.openqa.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Wtr-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-development
