[jboss-jira] [JBoss JIRA] (WFLY-12393) The jberet-core module should not depend on the javaee.api module

[Cheng Fang (Jira)]

    [ https://issues.jboss.org/browse/WFLY-12393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772736#comment-13772736 ] 

Cheng Fang edited comment on WFLY-12393 at 9/19/19 10:45 PM:
-------------------------------------------------------------

current {{org.jberet.jberet-core}} module.xml:

https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml

{{ javaee.api}} module.xml:
https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml#L25



was (Author: cfang):
current {{org.jberet.jberet-core}} module.xml:

https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml

> The jberet-core module should not depend on the javaee.api module
> -----------------------------------------------------------------
>
>                 Key: WFLY-12393
>                 URL: https://issues.jboss.org/browse/WFLY-12393
>             Project: WildFly
>          Issue Type: Bug
>          Components: Batch
>            Reporter: Brian Stansberry
>            Assignee: Cheng Fang
>            Priority: Major
>
> The javaee.api module is just a convenience wrapper around the various EE API modules it depends on and exports. The org.jberet.jberet-core module depends on this; it should be updated to depend on the specific APIs it need.
> Depending on javaee.api is problematic because in a server that has been slimmed using Galleon we only want to depend on modules that are actually needed and not pull in other API.



--
This message was sent by Atlassian Jira
(v7.13.5#713005)