wsdl2java mojo dependency clash with testDependencies - no workaround available - new config option needed

I have a scenarion where the tests require a saxon dependency which causes wsdl2java to bomb when accessing a binding customisation file using the -b option.

Because the wesl2java mojo always uses the test artifacts I can't have saxon missing for wsdl2java and present for the test run.

I think wsdl2java should allow an option to specify that teh compile artifacts/dependencies are used. In this way, a subset can be provided for the compile run where wsdl2java is used and the additional dependency can be specified in the test scope.