Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-20833

Manage core dependencies using wildfly-core-component-matrix instead of wildfly-core-parent

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Build System
    • None
    • ---
    • ---

      WF Core has this odd 'component-matrix-builder' module which generates a wildfly-core-component-matrix pom, using an approach very similar to how WildFly's boms/user boms are generated.

      AFAIK, this artifact isn't used. For example, https://mvnrepository.com/artifact/org.wildfly.core/wildfly-core-component-matrix/28.0.0.Final doesn't show any uses.

      But what it produces at a glance looks like a bom. So perhaps full WF should use it for production code dependency management, instead of importing wildfly-core-parent.

      Pros:

      This lets wildfly-core-parent evolve as needed without consideration for its use as a bom by some other project.

      Cons:

      I don't get the sense that anyone pays attention to this component-matrix-builder maven module. Now we'd need to, to ensure it does what we want it to do.

      But, if we're not willing to pay attention to that module, we should probably just remove it.

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: