[
https://issues.apache.org/jira/browse/XMLBEANS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292264#comment-17292264
]
Andreas Beeker commented on XMLBEANS-456:
-----------------------------------------
In POI 4.0.0 I've changed the way how the metadata lookup works - I think the
original problem is not an issue any more.
> No generated source for TypeSystemHolder -- breaks Maven plugin
> ---------------------------------------------------------------
>
> Key: XMLBEANS-456
> URL: https://issues.apache.org/jira/browse/XMLBEANS-456
> Project: XMLBeans
> Issue Type: Bug
> Components: Compiler
> Affects Versions: Version 2.3, Version 2.4
> Reporter: Boris Shingarov
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
