Closed SiKing closed 5 years ago
I just noticed that a new version was released. I updated my pom to:
<plugin> <groupId>com.lazerycode.selenium</groupId> <artifactId>driver-binary-downloader-maven-plugin</artifactId> <version>1.0.16</version> <configuration> <rootStandaloneServerDirectory>selenium/bin</rootStandaloneServerDirectory> <downloadedZipFileDirectory>selenium/zip</downloadedZipFileDirectory> <overwriteFilesThatExist>true</overwriteFilesThatExist> </configuration> <executions> <execution> <phase>pre-integration-test</phase> <goals> <goal>selenium</goal> </goals> </execution> </executions> </plugin>
A build on Jenkins says:
[INFO] Preparing to download Selenium Standalone Executable Binaries... [ERROR] File : 'operadriver_linux64.zip'. [ERROR] Expected file hash : 'a8528276dab36e5daa6213db16ac4ae227e8394d'. [ERROR] Actual file hash : 'c207c6916e20ecbbc7157e3bdeb4737f14f15fe3'. [INFO] Downloading 'operadriver_linux64.zip'... [INFO] Archive file 'operadriver_linux64.zip' is valid : true [INFO] Extracting binary 'operadriver'...
If I delete the selenium directory, then everything work fine.
selenium
Spent time researching something slightly related. I discovered that the above situation just prints the two ERROR lines, but continues to work as expected.
I just noticed that a new version was released. I updated my pom to:
A build on Jenkins says:
If I delete the
selenium
directory, then everything work fine.