Allow relative paths in pact publish task

Currently, when passing pactUrls to the publish task, the urls need to be absolute. It would be nice to pass in a relative path.

See https://github.com/pact-foundation/pact-js/issues/31 + https://github.com/pact-foundation/pact-node/commit/a5afdb17e2c3ca8acf6c6a2051e7575cc4bcb4b2#commitcomment-21360868 for background.

I suspect part of the complication is relativity to the underlying Ruby process, so we would need to convert to an absolute path under the hood anyway.

[bethesque]

The paths need to be relative to the directory you run the executable from - that might have been the issue. So you need to invoke the verifier using the relative path from the project root if possible.

Btw, there’s an issue to change the paths from options to space separated arguments, so we don’t have to do the comma separating thing.

[mboudreau]

@mefellows I’m looking into this one and thinking of adding something in the pact-util file that checks for paths/urls and then normalizes/resolves them if they’re valid.

Currently though, we’re a bit “laissez-faire” with the path validation as we do some minute checks on it, but nothing too concrete. I do agree that we need to have the ability to check relative vs absolute paths, however, should we also accept path shortcuts like ~/?

Also, when it comes to URLs, should we accept any protocols, or is it locked down to http(s)?

Trying to figure out the best way to do this as to implement it properly.