Bug 576037 - [selenium-remote-control] Split out client drivers.
Summary: [selenium-remote-control] Split out client drivers.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selenium-remote-control
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-23 03:40 UTC by Ding-Yi Chen
Modified: 2010-05-04 06:17 UTC (History)
1 user (show)

Fixed In Version: selenium-remote-control-1.0.3-5.20100318svn.fc13
Clone Of:
Environment:
Last Closed: 2010-05-04 06:17:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ding-Yi Chen 2010-03-23 03:40:32 UTC
Description of problem:
Upstream selenium-RC zip consists various client drivers like java, and python.

However, the current version of selenium-server does not have these drivers.
It will be helpful to have these drivers as sub-packages.



Version-Release number of selected component (if applicable):
selenium-server-1.0.2-0.4.20091211svn

How reproducible:
Always


Additional info:
selenium is now 1.0.3, consider upgrading to it?

Comment 1 Lubomir Rintel 2010-03-23 08:41:47 UTC
(In reply to comment #0)
> Description of problem:
> Upstream selenium-RC zip consists various client drivers like java, and python.
> 
> However, the current version of selenium-server does not have these drivers.
> It will be helpful to have these drivers as sub-packages.

Thank you for the report.

We currently ship just the perl client bindings, packaged separately in perl-Test-WWW-Selenium.

I did not package the other ones mostly due to personal time constraints. Thus I'd be thankful if you could help splitting the client drivers from the package.

If you can't do that, I'd prefer to start with client drivers that are most demanded; which ones do you use?

> selenium is now 1.0.3, consider upgrading to it?    

Selenium was updated to a SVN snapshot in Fedora 13 development branch (thus F-13 will ship with it). As much as I'd like to ship a release version, I was not able to find it anywhere since upstream seems to only ship binaries [1] and I could not find a tag in SVN.

[1] http://seleniumhq.org/download/

I currently don't plan to update Fedora 12 with a more recent build. Is there anything you miss in the older build (the reason behind shipping 1.0.3 in Fedora 13 was support for Firefox 3.6, Fedora 12 ships 3.5).

Comment 2 Ding-Yi Chen 2010-03-24 01:11:45 UTC
> We currently ship just the perl client bindings, packaged separately in
perl-Test-WWW-Selenium.

I would like to have java client driver.

> I did not package the other ones mostly due to personal time constraints. Thus
> I'd be thankful if you could help splitting the client drivers from the
> package.

Actually, I have tried to add java client driver myself, however,
it seems to depend on groovy, which in not yet in Fedora 12 and 13.

> I currently don't plan to update Fedora 12 with a more recent build. 
> Is there anything you miss in the older build (the reason behind shipping 1.0.3 in
> Fedora 13 was support for Firefox 3.6, Fedora 12 ships 3.5).   

Nothing, since I am new with selenium. :-) 
Just wondering whether you have time to do the update as well.

Comment 3 Lubomir Rintel 2010-03-30 09:43:41 UTC
(In reply to comment #2)
> > We currently ship just the perl client bindings, packaged separately in
> perl-Test-WWW-Selenium.
> 
> I would like to have java client driver.
> 
> > I did not package the other ones mostly due to personal time constraints. Thus
> > I'd be thankful if you could help splitting the client drivers from the
> > package.
> 
> Actually, I have tried to add java client driver myself, however,
> it seems to depend on groovy, which in not yet in Fedora 12 and 13.

Coincidentally, I maintain the groovy package, so I'm quite sure it is in Fedora 13 :)

I'll try to take a look at those (you're still welcome to do that yourself though :).

Comment 4 Fedora Update System 2010-03-30 12:28:34 UTC
selenium-remote-control-1.0.3-1.20100318svn.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/selenium-remote-control-1.0.3-1.20100318svn.fc13

Comment 5 Lubomir Rintel 2010-03-30 12:37:49 UTC
(In reply to comment #3)
> > Actually, I have tried to add java client driver myself, however,
> > it seems to depend on groovy, which in not yet in Fedora 12 and 13.
> 
> Coincidentally, I maintain the groovy package, so I'm quite sure it is in
> Fedora 13 :)

So, actually a groovy maven plugin was depended on, which we don't ship. Fortunately, it seems that it's not actually needed.

> I'll try to take a look at those (you're still welcome to do that yourself
> though :).    

Please look at the above link to the update system. The new package contains a java client driver subpackage. Could you please try it out and rate the update?

Thank you!

Comment 6 Ding-Yi Chen 2010-03-31 00:14:06 UTC
Thanks for processing the request.

I only have F-12 and EL-5 boxes, would you mind pushing groovy and the new selenium packages to at least one of the distroes? 

Thanks.

Comment 7 Lubomir Rintel 2010-03-31 11:32:46 UTC
(In reply to comment #6)
> I only have F-12 and EL-5 boxes, would you mind pushing groovy and the new
> selenium packages to at least one of the distroes? 

Rebases in stable releases are usually avoided without a compelling reason. The newly packaged java driver stuff might be a good reason for an update though, I'd prefer if you tested them first.

When it comes to EL-5 and groovy in F-12, the packages have a rather long dependency chain that would need to be pulled there. It's probably not even possible in EL-5 where we can't replace core components. Given Fedora 13 is almost at Beta stage now and will be released in a little over a month, I'm not going to do the extra work backporting takes (I'm fine with that if anyone else is interested in doing that).

That said, the, the F-13 and F-14 packages are just plain java stuff, thus will work on older distro versions as well, certainly on F-12. Something like

   yum --enablerepo=rawhide install selenium-java-client-driver groovy

might do the job of installing the necessary packages.

Comment 8 Fedora Update System 2010-05-03 07:31:27 UTC
selenium-remote-control-1.0.3-5.20100318svn.fc13,selenium-core-1.0.2-0.4.20100324svn.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/selenium-remote-control-1.0.3-5.20100318svn.fc13,selenium-core-1.0.2-0.4.20100324svn.fc13

Comment 9 Fedora Update System 2010-05-04 06:17:27 UTC
selenium-remote-control-1.0.3-5.20100318svn.fc13, selenium-core-1.0.2-0.4.20100324svn.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.