Closed mpkorstanje closed 7 years ago
Giving the source a quick look it appears that SeleniumServerMojo contains an annotation that causes the build to fork. It does not appear to be needed.
@Execute(phase = LifecyclePhase.TEST_COMPILE)
You are right, that should not be there.
Thanks for the quick fix. Cheers!
@rultor release, tag is 1.0.12
@rultor release, tag is
1.0.12
@ardesco OK, I will release it now. Please check the progress here
@rultor release, tag is
1.0.12
@ardesco Done! FYI, the full log is here (took me 4min)
@mpkorstanje it normally takes a couple of hours for it to propogate through to the maven download servers unless we are really lucky and it's a quiet time :)
You should be able to download it soon.
Excellent. I could do with a nap anyways. Cheers again!
When using selenium-standalone-server-plugin 1.0.11 bound to the initialization phase it appears that the plugin causes the build to execute test-compile twice. This is causing me some trouble as some resources from cucumber-jvm-parallel-plugin should only be generated once and appears to be related to issue #30.
First we see the build run up to initialize at which point we see:
Then we see the resource, compile, testResources, testCompile followed by:
At this point the download actually starts and is followed by
Then we see the resource, compile, testResources, testCompile come by again.
For what it is worth, binding the binary downloader to any other phases causes the same problem, but at different moments.