<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="">We also revert back to what we had before in QS, and work out a better solution from there.<div class=""><br class=""></div><div class="">—E<br class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 08 May 2018, at 16:06, Rostislav Svoboda &lt;<a href="mailto:rsvoboda@redhat.com" class="">rsvoboda@redhat.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">Tomaz mentioned Quickstarts as one of the reasons to have BOMs in WF and WF-CORE.<br class=""><br class=""></div>Eduardo should confirm that revert is fine for QS.<br class=""><br class=""></div>Rostislav<br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sat, May 5, 2018 at 11:25 AM, Kabir Khan <span dir="ltr" class="">&lt;<a href="mailto:kkhan@redhat.com" target="_blank" class="">kkhan@redhat.com</a>&gt;</span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Perhaps <a href="https://github.com/jboss/bom-builder-maven-plugin" rel="noreferrer" target="_blank" class="">https://github.com/jboss/bom-<wbr class="">builder-maven-plugin</a> can be used? I've not played with it<br class="">
<div class="HOEnZb"><div class="h5"><br class="">
&gt; On 4 May 2018, at 22:11, David Lloyd &lt;<a href="mailto:david.lloyd@redhat.com" class="">david.lloyd@redhat.com</a>&gt; wrote:<br class="">
&gt; <br class="">
&gt; I've created <a href="https://issues.jboss.org/browse/WFLY-10330" rel="noreferrer" target="_blank" class="">https://issues.jboss.org/<wbr class="">browse/WFLY-10330</a> and<br class="">
&gt; <a href="https://issues.jboss.org/browse/WFCORE-3803" rel="noreferrer" target="_blank" class="">https://issues.jboss.org/<wbr class="">browse/WFCORE-3803</a> to track this.<br class="">
&gt; <br class="">
&gt; On Fri, May 4, 2018 at 4:04 PM, Jason Greene &lt;<a href="mailto:jason.greene@redhat.com" class="">jason.greene@redhat.com</a>&gt; wrote:<br class="">
&gt;&gt; I agree. We can break the bom cycle a different way.<br class="">
&gt;&gt; <br class="">
&gt;&gt;&gt; On May 4, 2018, at 3:53 PM, David Lloyd &lt;<a href="mailto:david.lloyd@redhat.com" class="">david.lloyd@redhat.com</a>&gt; wrote:<br class="">
&gt;&gt;&gt; <br class="">
&gt;&gt;&gt; I propose we revert the component-matrix change.&nbsp; This change is<br class="">
&gt;&gt;&gt; ostensibly to help in the creation of a BOM for the client libraries<br class="">
&gt;&gt;&gt; and other dependent projects; however, the cost has turned out to be<br class="">
&gt;&gt;&gt; somewhat higher than expected.<br class="">
&gt;&gt;&gt; <br class="">
&gt;&gt;&gt; IntelliJ seems to be unable to cope with dependency changes in the<br class="">
&gt;&gt;&gt; project due to the use of import from the root POM.&nbsp; This means that<br class="">
&gt;&gt;&gt; the entire project must be force-reimported from time to time to keep<br class="">
&gt;&gt;&gt; dependencies up to date, and forgetting to do so can lead to<br class="">
&gt;&gt;&gt; development issues and lost time.<br class="">
&gt;&gt;&gt; <br class="">
&gt;&gt;&gt; Also, I've observed that Maven itself does not always correctly<br class="">
&gt;&gt;&gt; resolve versions anymore, when you're building from a submodule.&nbsp; I<br class="">
&gt;&gt;&gt; don't really know why this is the case but I suspect that it's due to<br class="">
&gt;&gt;&gt; some algorithmic ambiguity when the dependency tree is not linear like<br class="">
&gt;&gt;&gt; it used to be.<br class="">
&gt;&gt;&gt; <br class="">
&gt;&gt;&gt; I think that if we need to generate some BOM for use by external<br class="">
&gt;&gt;&gt; projects, it should be done as a separate step and artifact which<br class="">
&gt;&gt;&gt; acquires versions from the parent.&nbsp; I believe we had it this way at<br class="">
&gt;&gt;&gt; one point, didn't we?<br class="">
&gt;&gt;&gt; <br class="">
&gt;&gt;&gt; Anyway I think this change didn't work out, and we should undo it<br class="">
&gt;&gt;&gt; while it's still remotely possible.&nbsp; WDYT?<br class="">
&gt;&gt;&gt; <br class="">
&gt;&gt;&gt; --<br class="">
&gt;&gt;&gt; - DML<br class="">
&gt;&gt;&gt; ______________________________<wbr class="">_________________<br class="">
&gt;&gt;&gt; wildfly-dev mailing list<br class="">
&gt;&gt;&gt; <a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">
&gt;&gt;&gt; <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/<wbr class="">mailman/listinfo/wildfly-dev</a><br class="">
&gt; <br class="">
&gt; <br class="">
&gt; <br class="">
&gt; -- <br class="">
&gt; - DML<br class="">
&gt; ______________________________<wbr class="">_________________<br class="">
&gt; wildfly-dev mailing list<br class="">
&gt; <a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">
&gt; <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/<wbr class="">mailman/listinfo/wildfly-dev</a><br class="">
<br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
wildfly-dev mailing list<br class="">
<a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/<wbr class="">mailman/listinfo/wildfly-dev</a><br class="">
</div></div></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></div></body></html>