[jboss-jira] [JBoss JIRA] Updated: (AS7-922) Annotation Scanner should tell you which class could not be indexed

[ https://issues.jboss.org/browse/AS7-922?page=com.atlassian.jira.plugin.sy... ] Tomaz Cerar updated AS7-922: ---------------------------- Git Pull Request: https://github.com/jbossas/jboss-as/pull/46 Description: When trying to deploy ear application as throws you cryptic error msg "Invalid Magic" while it is trying to index annotations. currently stacktrace is like this: Caused by: java.lang.RuntimeException: Invalid Magic at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:389) at org.jboss.jandex.Indexer.index(Indexer.java:628) at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:102) The fix provided shows user which class failed indexing and in which archive. was: When trying to deploy ear application as throws you cryptic error msg "Invalid Magic" while it is trying to index annotations. Fix should probably be in jandex class Indexer line 389 (current beta7) where error message should also include name of publish class. currently stacktrace is like this: Caused by: java.lang.RuntimeException: Invalid Magic at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:389) at org.jboss.jandex.Indexer.index(Indexer.java:628) at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:102) I have fixed a reporting in my fork of as7, the fix was created in as7 as in this case we can also tell which archive contains bad class -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira