Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Cannot Reproduce
-
Version 2.3, Version 2.4
-
None
Description
According to the doc, Java classes are first generated in source form in the place specified by the "-src" flag, and then get compiled into a place specified by the "-d" flag.
However, this is not true for TypeSystemHolder. It is created in SchemaTypeSystemImpl.saveLoader(), by patching a template .class file.
This is a problem with the xmlbeans maven plugin. It trusts the xmlbeans doc and assumes that all the necessary code is available in the "src" place. It then automatically generates a .classpath for Eclipse containing the "src". Because the application program compiles against the generated interfaces, and those are present in "src", the problem does not get detected at compile time. But at runtime, the application will die with a NoClassDefFound.
I can not see how to work around this. The xmlbeans plugin provides no flexibility to allow changing the .classpath, so I can not just manually tell it to include the "-d" place.