<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 15 May 2018, at 12:28, Rostislav Svoboda <<a href="mailto:rsvoboda@redhat.com" class="">rsvoboda@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hi team.<br class=""><br class=""></div>WildFly and WildFly core generate component-matrix as part of the build now.<br class=""> <a href="https://issues.jboss.org/browse/WFLY-10365" class="">https://issues.jboss.org/browse/WFLY-10365</a><br class=""><div class=""><div class="gmail-flooded gmail-action-body"><p class="">We should also consider automated propagation of current WildFly master component versions into WildFly BOMs - <a href="https://github.com/wildfly/boms" class="external-link" rel="nofollow">https://github.com/wildfly/boms</a>. I'm especially interested in <a href="https://github.com/wildfly/boms/tree/master/client" class="external-link" rel="nofollow">https://github.com/wildfly/boms/tree/master/client</a></p>Currently, the sync is rather complicated (manual) and not at all intuitive to implement.</div></div></div></div></blockquote><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class="gmail-flooded gmail-action-body">Tomaz did great job on BOMs but with his departure nothing is really happening in this area.<br class=""></div><div class="gmail-flooded gmail-action-body"><br class=""></div></div></div></div></blockquote><div><br class=""></div><div>FYI <a href="https://github.com/emmartins/boms/tree/component-matrix" class="">https://github.com/emmartins/boms/tree/component-matrix</a></div></div><br class=""><div class="">Unfortunately there are still a few manual dependencies needed to be declared atm, cause if we import the component matrix (CM) in a BOM dependency management, e.g. wildly-tools, it will add all CM dependencies. BOM “import" only allows configuration of exclusions, not inclusions…</div><div class=""><br class=""></div><div class="">A possible workaround is to enhance the BOM builder plugin with “includes” functionality, this way the BOMs project could split CM into smaller BOM CMs, each declaring only the dependencies needed by a BOM, which would then import it.</div><div class=""><br class=""></div><div class="">By the way additional BOMs providing the EE8 APIs supported by WFLY 13 are also incoming.</div><div class=""><br class=""></div><div class="">—E</div><div class=""><br class=""></div></body></html>