in xjc the user classpath should be initialized prior to the "parseArguments" to allow for proper custom plugin detection

[sergejkv]

In the com.sun.tools.xjc.Driver

the user class path initialization :

   final ClassLoader contextClassLoader = SecureLoader.getContextClassLoader();
    SecureLoader.setContextClassLoader(opt.getUserClassLoader(contextClassLoader));

should be moved above the:

opt.parseArguments(args);

so the custom plugins could be properly detected in the "Options.findServices".

The current workaround in to add the custom xjc plugins to the xjc class path (as opposed to the xjc --classpath parameter).