using maven parameter or maven plugin, you can define which settings.xml should be used by ShrinkWrap Resolver in the arquillian-phantom-driver project. For this, there are system properties that can be set: GitHub - shrinkwrap/resolver: ShrinkWrap Resolvers
So you are mainly interested in the first two properties. arquillian-phantom-driver uses an older version of SWR (2.2.2) where is a bug when the property "org.apache.maven.global-settings" is used. So you can either use only "org.apache.maven.user-settings" or define ShrinkWrap Resolver BOM with the latest version in your pom file and then you can use both properties.
Yeah, good idea. I've created an issue for this, so it should be incorporated in the next release hopefully. [ARQ-2074] Check if binary is already executable before trying to chmod it regardless - JBoss Issue Tracker
Thanks for the response Matous - I will give your scenario 1 solution a go soon.
Regarding Scenario 2 - That isn't the piece of code that throws for me (although it does look like it would) - it's this line which I see in my stack trace: arquillian-phantom-driver/PhantomJSBinary.java at master · qa/arquillian-phantom-driver · GitHub
Any idea when the next release targeted for?
sorry for the delay. I've fixed it in both projects Drone and arquillian-phantom-driver and released new versions. Everything is in Maven central, so you can give it a try - the Drone version you are interested in is 2.1.0.Alpha2