[wildfly-dev] Re: Updates to how dependency management works in main
Jeff: Only the WildFly BOMs builders need to be updated, to replace the wildfly-parent
import with all the new internal BOMs. The BOMs built do not import anything.
Brian: Can you please list all the artifactIds that provide same set of the old
dependencyManagement, so I update the WildFly BOMs Builders?
—E
On 30 May 2022, at 13:12, Jean-Frederic Mesnil
<jmesnil(a)redhat.com> wrote:
Hi Brian,
How does these changes affect the WildFly BOMs[1] that are meant for user consumptions
(as opposed to WildFly internal bill of material)?
These boms directly import org.wildfly:wildfly-parent:pom[2] (which brings more than what
a WildFly user actually needs). They will be affected whenever we move WildFly
“user-facing” dependencies outside of its parent.
Have you considered moving these “user” BOMs into WildFly?
In particular, after your changes, it might be simpler to provide such BOMs for the
different feature packs (WildFly Preview in particular).
Best, Regards,
Jeff
[1] https://github.com/wildfly/boms
[2]
https://github.com/wildfly/boms/blob/725e33099ffe8676ad97944d8c54d4a07bdf...
--
Jeff Mesnil
Principal Software Engineer
Red Hat
http://jmesnil.net/