This fixes the "annotation element JavaDoc" problem, as I can now run the simple test program okay.
However, this breaks our existing code when I attempt to run our full application.

Running:

output.addInterface("com.blah.blah.blah.ConfigAware<T>"); // output is of type InterfaceCapableSource<?>

gives the following exception stack trace:

java.lang.IllegalArgumentException: Invalid identifier : >ConfigAware<T><
	at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:247)
	at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2793)
	at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newName(AST.java:2443)
	at org.jboss.forge.roaster.model.impl.AbstractInterfaceCapableJavaSource.addInterface(AbstractInterfaceCapableJavaSource.java:94)
	at com.tccc.kos.sdk.generator.builder.TypeBase.copyInterfaces(TypeBase.java:320)
	at com.tccc.kos.sdk.generator.builder.TypeClass.parse(TypeClass.java:34)

It happens because the target class implements the ConfigAware<T> interface, which contains the <T> generic.

Any ideas?
Was there a recent change to this code? (It works as expected in version 2.26.0.Final)

I also get this error when I use v2.27.0.Final, so it has something to do with going from 2.26.0 to 2.27.0.

I see one thing that changed is org.eclipse.jdt.core, which went from v3.30.0 to v3.31.0.

@rob-stoecklein good catch! I pushed a fix to master and rebased this PR. Can you give it a try now? I'll release the next version once you confirm it's okay

@gastaldi It now works like a champ -- thanks!

We do you think 2.28.0 will be pushed to the Central repo?

@rob-stoecklein I just released to Central, should be there in a few minutes

It's there now, enjoy! https://repo1.maven.org/maven2/org/jboss/forge/roaster/roaster-jdt/2.28.0.Final/roaster-jdt-2.28.0.Final.pom

Excellent -- thank you!