[ https://issues.jboss.org/browse/JBEE-180?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated JBEE-180: ----------------------------- Description: Currently JBMS fails to create automodule name out of our artifacts as we have version of the spec in the name of the jar. Elegant solution would be to add Automatic-Module-Name manifest entry to the artifacts. Biggest question is what name of the module should be. One of suggestions was that until we have offical EG guidline what module name for such spec jars should be, we could use "beta." prefix to note that this name wont be there to stay. If spec API is one that is upgradable in JDK itself (such as java.transaction) we should use same name that is already used in JDK. But before we go on and do that, we should make sure that such jars work with jdk9 at all, as there is already known issue with JTA see http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008779.html for more details. was: Currently JBMS fails to create automodule name out of our artifacts as we have version of the spec in the name of the jar. Elegant solution would be to add Automatic-Module-Name manifest entry to the artifacts. Biggest question is what name of the module should be. One of suggestions was that until we have offical EG guidline what module name for such spec jars should be, we could use "beta." prefix to note that this name wont be there to stay. But before we go on and do that, we should make sure that such jars work with jdk9 at all, as there is already known issue with JTA see http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008779.html for more details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)