[ https://issues.jboss.org/browse/WFLY-6460?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFLY-6460: ----------------------------------------- Looking at https://github.com/jboss/jboss-json-api_spec/pull/6 and https://github.com/jamezp/wildfly/commit/a66b00225932a75d0aae09b9637a66b9... My original complain is that dist/target/wildfly-12.0.0.Alpha1-SNAPSHOT/modules//system/layers/base/javax/json/api/main/module.xml is defined as {code} <module name="javax.json.api" xmlns="urn:jboss:module:1.6"> <properties> <property name="jboss.api" value="public"/> </properties> <dependencies> <module name="org.glassfish.javax.json" export="false"> <exports> <include-set> <path name="javax/json"/> <path name="javax/json/spi"/> <path name="javax/json/stream"/> </include-set> </exports> </module> </dependencies> </module> {code} So not really using https://github.com/jboss/jboss-json-api_spec ... but your pr is tackling that now. https://github.com/jboss/jboss-json-api_spec/blame/master/pom.xml#L94 says Automatic-Module-Name is set as part of Update to JSR 374 JSON-P 1.1. Java 9+ effort could have separate commits not to mix it with EE8 effort side comment I have is to https://github.com/jboss/jboss-json-api_spec repo name and GAV, shouldn't it really say jsonp ? Especially now when jsonb is in game :) -- This message was sent by Atlassian JIRA (v7.5.0#75005)