This should fix issue #17766. Please take into account that this solution would append to any CLASSPATH env var already provided in configuration. Another solution would be to simply leave the provided classpath env var as it is in such cases. Then the caller would have to include all maven related classpath items. In either case an amendment of the goal documentation should be taken into consideration. Please guide me on how to do so if you find this useful.
Regards
Clemens Quoß
Comment From: pivotal-issuemaster
@cquoss Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: pivotal-issuemaster
@cquoss Thank you for signing the Contributor License Agreement!
Comment From: philwebb
We discussed this today as a team and we've decided that unfortunately there are too many downsides to used the environment variable. We think the pathing jar is the best long term solution as it will work with both forked and non-forked processes. We'll leave #17766 open to track that.
Thanks anyway for the idea and the PR.