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?
Probably some or most of the boms could use wildfly-ee-feature-pack-parent instead, but perhaps we should defer making such a change until we decide whether we want to continue to use the wildfly-[xxx-]feature-pack-parent pom's I used or instead create separate poms specific to this purpose.
—E
> On 30 May 2022, at 13:12, Jean-Frederic Mesnil <jmesnil@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).
I hadn't considered that, no, but it's a reasonable thing to consider. I haven't really thought about how that would fit with any longer term thinking about how we do provisioning, maintenance releases etc.
>
> Best, Regards,
> Jeff
>
>
> [1] https://github.com/wildfly/boms
> [2] https://github.com/wildfly/boms/blob/725e33099ffe8676ad97944d8c54d4a07bdf6ea7/jakartaee8/pom.xml#L56-L62
>
> --
> Jeff Mesnil
> Principal Software Engineer
> Red Hat
> http://jmesnil.net/
>