[WFLY-16956] Move jboss-ejb-client-legacy to the standard-ee bom as s… #16037
Conversation
…ome deliverables associated with WildFly include it
github-actions
bot
added
the
deps-ok
|
Is anything blocking this one from being merged? |
|
@jbliznak It needs someone to approve it. You're welcome to do that. :) |
There was a problem hiding this comment.
OK, I thought you don't need one :)
this is the difference in particular BOM after the change jbliznak/test-boms@aa52228...bfcd431
it is a bit more than expected and order of dependencies can matter but it still looks ok to me, non-legacy BOM (https://repo1.maven.org/maven2/org/wildfly/wildfly-ejb-client-bom/27.0.0.Alpha4/wildfly-ejb-client-bom-27.0.0.Alpha4.pom) also has those jakarta APIs in there before actual client dependency so at least they are now more similar.
|
Thanks for the review / test of the result @jbliznak! The folks who have permissions to merge things try to resist the temptation to merge our own stuff if it hasn't gotten a review. I think we're mostly successful. ;) |
…ome deliverables associated with WildFly include it
https://issues.redhat.com/browse/WFLY-16956