Description Markus Keller 2015-08-13 12:19:46 EDT

4.6.0.I20150805-2000

Bad AST node structure:
- parent [34, 427] org.eclipse.jdt.core.dom.EnumDeclaration
   previous [166, 169] org.eclipse.jdt.core.dom.EnumConstantDeclaration
   bodyDeclarations [136, 146] org.eclipse.jdt.core.dom.FieldDeclaration

----------------------------------- SOURCE BEGIN -------------------------------------
    //Example: Code fragment
    @XmlEnum(String.class)
    public enum Card { CLUBS, DIAMONDS, HEARTS, SPADES }

    <!-- Example: XML Schema fragment -->
    <xs:simpleType name="Card">
      <xs:restriction base="xs:string"/>
        <xs:enumeration value="CLUBS"/>
        <xs:enumeration value="DIAMONDS"/>
        <xs:enumeration value="HEARTS"/>
        <xs:enumeration value="SPADES"/>
    </xs:simpleType>

----------------------------------- SOURCE END -------------------------------------

java.lang.IllegalStateException: Bad AST node structure
	at org.eclipse.jdt.core.dom.ASTConverter.convert(ASTConverter.java:1419)
	at org.eclipse.jdt.core.dom.CompilationUnitResolver.convert(CompilationUnitResolver.java:295)
	at org.eclipse.jdt.core.dom.ASTParser.internalCreateAST(ASTParser.java:1216)
	at org.eclipse.jdt.core.dom.ASTParser.createAST(ASTParser.java:812)
	at org.eclipse.jdt.internal.ui.refactoring.reorg.PasteAction$TextPaster$ParsedCu.parseCus(PasteAction.java:378)
...

The given source is embedded in a <pre> section in the Javadoc of javax.xml.bind.annotation.XmlEnumValue. Found the problem because the formatter creates an AST for code snippets, and I had the debug/dom/ast trace option enabled.