| Summary: | Errors running builder Java Builder: Can't find bundle for XMLSchemaMessages | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Trevor Robinson <trevor> |
| Component: | APT | Assignee: | Generic inbox for the JDT-APT component <jdt-apt-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | eclipse, jarthana |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | stalebug | ||
|
Description
Trevor Robinson
As a workaround (that does not address the underlying issue), I was able to specify fullyAnnotationConfigured=true as an annotation processing property for the affected projects. This bypasses any XML processing in JPAMetaModelEntityProcessor.init(). I don't think this has anything to do with APT as such; APT is just loading processors like it's supposed to. The error is either with your project configuration or with your installed bundles. This bug probably needs to be reassigned to whatever component owns the Hibernate JPA processor. The stack suggests that: 1. annotation processing is active. 2. org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor is being found on the annotation processing classpath. 3. that processor is initializing and trying to load schema. 4. it is failing to parse its schema, and trying to produce an error message. 5. it is failing when trying to format the error message, because of a missing bundle. So I think there are two questions that you might want to look into. First, how come org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor is on the annotation processor classpath? It doesn't sound like you're trying to use it, so I'm wondering why it's there at all. Does your project have an unintended facet? Second, given that you clearly have many org.apache.xerces classes in the annotation processor classpath, how come it's not finding org.apache.xerces.impl.msg.XMLSchemaMessage? What bundle should that be part of, and why do you have some but not all of the Xerces bundles? This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |