<div><div dir="auto">I am going to release 13 Beta1 of BOMs and Quickstarts today not using component-matrix.</div><div dir="auto"><br></div><div dir="auto">—E</div><br><div class="gmail_quote"><div>On Fri, 18 May 2018 at 09:48, Eduardo Martins <<a href="mailto:emartins@redhat.com">emartins@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="auto">Honestly I am not sure it’s worth the risks (which Petr implied), trials with quickstarts with boms from my branch using the component-matrix resulted in some issues. If it turns out we need to add exclusions it’s not an improvement over explicit defining dependencies, which could be seen as “inclusions”.</div></div><div><div dir="auto"><br></div><div dir="auto">—E</div></div><div><br><div class="gmail_quote"><div>On Fri, 18 May 2018 at 08:27, Rostislav Svoboda <<a href="mailto:rsvoboda@redhat.com" target="_blank">rsvoboda@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>OK, so we need both independence and quick/easy/automated way to used the same versions in BOMs as in wf component matrix.<br><br>To keep the wf boms independent of wf component matrix we would probably need explicitely defined versions in BOMs + bom-generator similar to <a href="https://github.com/wildfly/wildfly-component-matrix-plugin" target="_blank">https://github.com/wildfly/wildfly-component-matrix-plugin</a> which consumes wf component matrix when needed.<br><br></div></div><div><div>Rostislav<br></div><div><br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 17, 2018 at 4:41 PM, Tomaž Cerar <span><<a href="mailto:tomaz.cerar@gmail.com" target="_blank">tomaz.cerar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><span>>
Possible approaches:<br><div>> 1) wildfly/boms project could consume the
component matrix versions without any required interaction besides just
declaring version of WildFly component matrix and then building
wildfly/boms <br></div><div><br></div></span><div>keep in mind that having wildfly/boms seperate from wildfly main release lifecycle is and welcome addition.</div><div>Quickstarts depend solely on boms, and as such should be avalible before WildFly server release is done, so QS can be developed and tested (also on OpenShift)</div><div><br></div><div>--</div><div>tomaz<br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_-217144094033268336m_-2864736537037083617h5">On Tue, May 15, 2018 at 1:28 PM, Rostislav Svoboda <span><<a href="mailto:rsvoboda@redhat.com" target="_blank">rsvoboda@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-217144094033268336m_-2864736537037083617h5"><div><div>Hi team.<br><br></div>WildFly and WildFly core generate component-matrix as part of the build now.<br> <a href="https://issues.jboss.org/browse/WFLY-10365" target="_blank">https://issues.jboss.org/browse/WFLY-10365</a><br><div><div class="m_-217144094033268336m_-2864736537037083617m_-1311868927327758416m_6263547029864072597gmail-action-body m_-217144094033268336m_-2864736537037083617m_-1311868927327758416m_6263547029864072597gmail-flooded"><p>We should also consider automated propagation of current WildFly master component versions into WildFly BOMs - <a href="https://github.com/wildfly/boms" class="m_-217144094033268336m_-2864736537037083617m_-1311868927327758416m_6263547029864072597external-link" rel="nofollow" target="_blank">https://github.com/wildfly/boms</a>. I'm especially interested in <a href="https://github.com/wildfly/boms/tree/master/client" class="m_-217144094033268336m_-2864736537037083617m_-1311868927327758416m_6263547029864072597external-link" rel="nofollow" target="_blank">https://github.com/wildfly/boms/tree/master/client</a></p>Currently, the sync is rather complicated (manual) and not at all intuitive to implement.<br></div><div class="m_-217144094033268336m_-2864736537037083617m_-1311868927327758416m_6263547029864072597gmail-action-body m_-217144094033268336m_-2864736537037083617m_-1311868927327758416m_6263547029864072597gmail-flooded">Tomaz did great job on BOMs but with his departure nothing is really happening in this area.<br></div><div class="m_-217144094033268336m_-2864736537037083617m_-1311868927327758416m_6263547029864072597gmail-action-body m_-217144094033268336m_-2864736537037083617m_-1311868927327758416m_6263547029864072597gmail-flooded"><br>Possible approaches:<br>1) wildfly/boms project could consume the component matrix versions without any required interaction besides just declaring version of WildFly component matrix and then building wildfly/boms<br><br>2) generating -SNAPSHOT versions of WildFly BOMs as part of WildFly build (going back I know) ++ publishing just the final BOMs to <a href="https://github.com/wildfly/boms" target="_blank">https://github.com/wildfly/boms</a> ? </div><br></div><div>Comments / suggestions ?<br><br></div><div>Regards.<span class="m_-217144094033268336m_-2864736537037083617m_-1311868927327758416HOEnZb"><font color="#888888"><br></font></span></div><span class="m_-217144094033268336m_-2864736537037083617m_-1311868927327758416HOEnZb"><font color="#888888"><div>Rostislav<br></div></font></span></div>
<br></div></div><span>_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br></span></blockquote></div><br></div>
</blockquote></div><br></div>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div></div></blockquote></div></div>