Bug 734475 - selenium-server BASE_JARS do not include org.apache.commons.codec.binary.Base64
Summary: selenium-server BASE_JARS do not include org.apache.commons.codec.binary.Base64
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: selenium-core
Version: 14
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-30 14:20 UTC by Tim Coote
Modified: 2012-08-16 14:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 14:02:12 UTC


Attachments (Terms of Use)

Description Tim Coote 2011-08-30 14:20:42 UTC
Description of problem:
The default selenium-server set up cannot find the Base64 encoder, which it requires for screen capture functionality (see line 3 here: http://bit.ly/o8peWG).

The workaround that I've used is to add a ~/.selenium-serverrc of one line:
BASE_JARS="$BASE_JARS apache-commons-codec.jar"

Version-Release number of selected component (if applicable):
selenium-server-1.0.3-7.20100318svn.fc14.noarch

How reproducible:
Consistent

Steps to Reproduce:
1. Install selenium-server and run selenium-server in a terminal window
2. from another terminal run a test against selenium-server that calls CaptureScreenshotToStringCommand (I'm actually using robotframework to do this).
3. screenshot should be captured into a file in the current directory
  
Actual results:
At stage 2, a Warning is produced:
POST /selenium-server/driver /HTTP/1.1
java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64

Expected results:
A Base64 encoding of a screenshot should be dumped into a file.

Additional info:
I can provide a simple script for running the robotframework test, but figured that there ought to be some regression test for selenium-server that I'm not familiar with that ought to throw this error, and there wouldn't be much point in asking the fedora team to learn a new tool. I think that there's enough info here to easily reproduce, the bug, but feel free to prod me if you think that I've been too lazy.

Comment 1 Fedora End Of Life 2012-08-16 14:02:15 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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