#27 Include problematic path in exception message

[DevInsanity]

No description provided.

[rfscholte]

The resulting message is a bit cryptic, I'd prefer prefer {} not allowed on the path, only outputDirectories and jars are accepted. This makes it a clear human readable message.

[DevInsanity]

The resulting message is a bit cryptic, I'd prefer prefer {} not allowed on the path, only outputDirectories and jars are accepted. This makes it a clear human readable message.

That's fair. The initial change was just what I'd done locally to figure out my own problem. I've adjusted the message.