[jboss-jira] [JBoss JIRA] (WFLY-9576) Dependencies with module-info.class cause warnings on application start

[Brian Stansberry (Jira)]

     [ https://issues.jboss.org/browse/WFLY-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved WFLY-9576.
------------------------------------
    Fix Version/s: 13.0.0.Final
       Resolution: Duplicate Issue


As noted in my comment on WFLY-9608, I believe this is fixed in the Jandex used since WildFly 13.

> Dependencies with module-info.class cause warnings on application start
> -----------------------------------------------------------------------
>
>                 Key: WFLY-9576
>                 URL: https://issues.jboss.org/browse/WFLY-9576
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: Yannick Majoros
>            Assignee: Jason Greene
>            Priority: Major
>             Fix For: 13.0.0.Final
>
>
> We have an issue when deploying any application that has dependencies that have a module-info.class. We had a similar problem in Wildfly-swarm.
> Here is the stack:
> {code}
> 11:10:36,986 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0003: Could not index class module-info.class at /content/file-hosting-application-1.0-SNAPSHOT.ear/file-hosting-web-1.0-SNAPSHOT.war/WEB-INF/lib/javax.json-api-1.1.jar: java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 18
>         at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:1417)
>         at org.jboss.jandex.Indexer.index(Indexer.java:1451)
>         at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:99)
>         at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51)
>         at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
>         at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
>         at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
> {code}
> I submitted a patch for wildfly-swarm (https://issues.jboss.org/browse/SWARM-1500), but the real solution would be to upgrade Jandex to 2.0.2. Is this planned?



--
This message was sent by Atlassian Jira
(v7.12.1#712002)