Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
Maven home: /home/kshaw/java/apache-maven-3.0.4
Java version: 1.7.0_40, vendor: Oracle Corporation
Java home: /opt/jdk1.7.0_40/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.8.13-100.fc17.x86_64", arch: "amd64",
family: "unix"
On 10/05/2013 11:19 AM, Mauro Talevi wrote:
What's your mvn -v?
On 05/10/2013 19:18, Kendall Shaw wrote:
Hi,
Sorry about sending the failure notice to the list.
I'm sort of using master by accident. But, to get it to build and
have tests succeed I changed:
PropertyWebDriverProvider.createDriver so that the case statement has
default: at the end and defaults to firefox.
PropertyWebDriverProviderTest.shouldSupportFirefoxByDefault to save
and then clear the browser property before running the test (it was
set to htmlunit somehow). I then restore the property if it is not null
That is not the end of the story, but I stopped after it completed
successfully.
After failure, and running mvn install -rf :jbehave-web-selenium, the
browser property was set to "htmlunit". After the fixes I mention
above (except for checking if the property was null), apparently the
browser property was unset. I can't make sense of that. But, I think
it means that the browser property is different if you run the entire
suite vs. the selenium test. Maybe an unintentional dependency,
My employer has rights to my brain so I cannot provide a diff... sorry.
Kendall
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
ThisIsHardToRead, asIsThis. This_is_easier, unless_it_is_underlined.
This.is.easy. This-is-easy-too. Almost as easy to read as this.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
