-
Bug
-
Resolution: Done
-
Major
-
None
-
None
WildFly 34 introduces dependency management changes that removes commons-logging from being a managed artifact, and this means the user BOM Builder plugin no longer removes its exclusion from RESTeasy and Apache HTTP Client artifacts, and ultimately this means apps using our EE BOMs and such clients now need to add an explicit dependency to our fork org.jboss.logging:commons-logging-jboss-logging, which is the common-logging replacements used by WildFly modules.
Please note that for standalone clients, for instance when doing integration tests, it's irrelevant to use our fork or the original commons-logging, yet it should be easier for projects to maintain a managed dependency.
We have the following quickstarts using the affected clients:
- helloworld-mutual-*
- jaxrs-*
- logging
- microprofile-lra
The affected quickstarts use the clients in integration tests, and should add a dependency to our fork to minimize impact on maintenance.