@mattwynne I agree that having a docker base image is quite a good idea. I've had some troubles pinning down bugs in aruba with jruby - since I don't use rvm + only the latest mri ruby - so having a Docker image available is very welcome.
@e2 I like the idea to have
docker-compose, but is python required to run it?
excuse for absorbing more and more dependencies into the project.
I agree! Besides that, I think we need to find a balance between documentation and dependencies. All problematic dependencies are
I think we can handle this by flagging all scenarios with external deps as
@documentation-only or so. Then exclude them in a default cucumber run (cucumber.yml) and run them only in container/CI. I like the idea of having living documentation and don't want to "reduce" - sorry no better idea how to name it - our feature files' value for the project.
I think excluding them is a OK compromise.
@all Is there anybody interested in taking over maintainership of jarib/childprocess#104? It's a ruby library to run commands on MRI Ruby, JRuby, Linux, Windows, ... We use it in
Unfortunately I don't have much spare time nowadays. I want to spent the bit of my spare time on
aruba. So any help is welcome.