[
https://issues.jboss.org/browse/WFLY-12376?page=com.atlassian.jira.plugin...
]
Eduardo Martins moved JBEAP-17394 to WFLY-12376:
------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-12376 (was: JBEAP-17394)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: BOM
(was: BOM)
Affects Version/s: 17.0.1.Final
(was: 7.3.0.CD17)
wildfly-ejb-client-bom does not manage
org.jboss.ejb3:jboss-ejb3-ext-api anymore
--------------------------------------------------------------------------------
Key: WFLY-12376
URL:
https://issues.jboss.org/browse/WFLY-12376
Project: WildFly
Issue Type: Bug
Components: BOM
Affects Versions: 17.0.1.Final
Reporter: Eduardo Martins
Assignee: Eduardo Martins
Priority: Blocker
When using {{org.jboss.eap:wildfly-ejb-client-bom:7.3.0.CD17}},
{{org.jboss.ejb3:jboss-ejb3-ext-api}} is not provided anymore. This is a regression
compared to {{org.jboss.eap:wildfly-ejb-client-bom:7.3.0.CD16}}.
From the user point of view, this will mean they will have to modify their existing
applications to include version of this dependency, which is pretty bad UX.
The BOM is the only recommended and documented way to consume EJB client libraries in
standalone applications, please see [Developing EJB
Applications|https://access.redhat.com/documentation/en-us/red_hat_jboss_...].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)