<div dir="ltr">Also this Blocker is dependent on a JBoss Modules upgrade that David is currently working on - <a href="https://issues.jboss.org/browse/WFCORE-3799">https://issues.jboss.org/browse/WFCORE-3799</a></div><br><div class="gmail_quote"><div dir="ltr">On Thu, 10 May 2018 at 17:28 Darran Lofthouse <<a href="mailto:darran.lofthouse@redhat.com">darran.lofthouse@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 dir="ltr">FYI I am planning a set of WildFly Elytron component upgrades tomorrow morning.<div><br></div><div>Regards,</div><div>Darran Lofthouse.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, 10 May 2018 at 17:25 Kabir Khan <<a href="mailto:kkhan@redhat.com" target="_blank">kkhan@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Here are the pull requests to move the version properties and dependency management back into the root pom.xml and getting rid of the component-matrix.<br>
<br>
<a href="https://github.com/wildfly/wildfly-core/pull/3275" rel="noreferrer" target="_blank">https://github.com/wildfly/wildfly-core/pull/3275</a><br>
<a href="https://github.com/wildfly/wildfly/pull/11200" rel="noreferrer" target="_blank">https://github.com/wildfly/wildfly/pull/11200</a><br>
<br>
We need to release a Beta of core tomorrow so it can get in for the feature freeze. <br>
<br>
I am dabbling with generating the component-matrix contents by other means.<br>
<br>
<br>
<br>
> On 9 May 2018, at 07:30, Petr Sakar <<a href="mailto:psakar@redhat.com" target="_blank">psakar@redhat.com</a>> wrote:<br>
> <br>
> Plugin is used by EAP maven repo build to generate eap-runtime bom eg [1] based on the feature packs dependency tree.<br>
> <br>
> Relevant configuration is [2] <br>
> <br>
> Petr<br>
> <br>
> [1] <a href="http://download-ipv4.eng.brq.redhat.com/brewroot/repos/jb-eap-7.2-maven-build/latest/maven/org/jboss/bom/eap-runtime-artifacts/7.2.0.CD12.CR2/eap-runtime-artifacts-7.2.0.CD12.CR2.pom" rel="noreferrer" target="_blank">http://download-ipv4.eng.brq.redhat.com/brewroot/repos/jb-eap-7.2-maven-build/latest/maven/org/jboss/bom/eap-runtime-artifacts/7.2.0.CD12.CR2/eap-runtime-artifacts-7.2.0.CD12.CR2.pom</a><br>
> <br>
> [2] <a href="http://git.app.eng.bos.redhat.com/git/jboss-eap/maven-repository-testsuite.git/tree/repository-content/dependency-lists/eap-runtime-artifacts/pom.xml?h=eap-7.2.0.CD12#n105" rel="noreferrer" target="_blank">http://git.app.eng.bos.redhat.com/git/jboss-eap/maven-repository-testsuite.git/tree/repository-content/dependency-lists/eap-runtime-artifacts/pom.xml?h=eap-7.2.0.CD12#n105</a><br>
> <br>
> On 05/08/2018 05:45 PM, Brian Stansberry wrote:<br>
>> Hi Paul and Petr,<br>
>> <br>
>> Do you know of any uses of this plugin we could learn from?<br>
>> <br>
>> Best regards,<br>
>> Brian<br>
>> <br>
>> On Sat, May 5, 2018 at 4:25 AM, Kabir Khan <<a href="mailto:kkhan@redhat.com" target="_blank">kkhan@redhat.com</a>> wrote:<br>
>> Perhaps <a href="https://github.com/jboss/bom-builder-maven-plugin" rel="noreferrer" target="_blank">https://github.com/jboss/bom-builder-maven-plugin</a> can be used? I've not played with it<br>
>> <br>
>> > On 4 May 2018, at 22:11, David Lloyd <<a href="mailto:david.lloyd@redhat.com" target="_blank">david.lloyd@redhat.com</a>> wrote:<br>
>> > <br>
>> > I've created <a href="https://issues.jboss.org/browse/WFLY-10330" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/WFLY-10330</a> and<br>
>> > <a href="https://issues.jboss.org/browse/WFCORE-3803" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/WFCORE-3803</a> to track this.<br>
>> > <br>
>> > On Fri, May 4, 2018 at 4:04 PM, Jason Greene <<a href="mailto:jason.greene@redhat.com" target="_blank">jason.greene@redhat.com</a>> wrote:<br>
>> >> I agree. We can break the bom cycle a different way.<br>
>> >> <br>
>> >>> On May 4, 2018, at 3:53 PM, David Lloyd <<a href="mailto:david.lloyd@redhat.com" target="_blank">david.lloyd@redhat.com</a>> wrote:<br>
>> >>> <br>
>> >>> I propose we revert the component-matrix change. This change is<br>
>> >>> ostensibly to help in the creation of a BOM for the client libraries<br>
>> >>> and other dependent projects; however, the cost has turned out to be<br>
>> >>> somewhat higher than expected.<br>
>> >>> <br>
>> >>> IntelliJ seems to be unable to cope with dependency changes in the<br>
>> >>> project due to the use of import from the root POM. This means that<br>
>> >>> the entire project must be force-reimported from time to time to keep<br>
>> >>> dependencies up to date, and forgetting to do so can lead to<br>
>> >>> development issues and lost time.<br>
>> >>> <br>
>> >>> Also, I've observed that Maven itself does not always correctly<br>
>> >>> resolve versions anymore, when you're building from a submodule. I<br>
>> >>> don't really know why this is the case but I suspect that it's due to<br>
>> >>> some algorithmic ambiguity when the dependency tree is not linear like<br>
>> >>> it used to be.<br>
>> >>> <br>
>> >>> I think that if we need to generate some BOM for use by external<br>
>> >>> projects, it should be done as a separate step and artifact which<br>
>> >>> acquires versions from the parent. I believe we had it this way at<br>
>> >>> one point, didn't we?<br>
>> >>> <br>
>> >>> Anyway I think this change didn't work out, and we should undo it<br>
>> >>> while it's still remotely possible. WDYT?<br>
>> >>> <br>
>> >>> --<br>
>> >>> - DML<br>
>> >>> _______________________________________________<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>
>> > <br>
>> > <br>
>> > <br>
>> > -- <br>
>> > - DML<br>
>> > _______________________________________________<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>
>> <br>
>> <br>
>> _______________________________________________<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>
>> <br>
>> <br>
>> <br>
>> -- <br>
>> Brian Stansberry<br>
>> Manager, Senior Principal Software Engineer<br>
>> Red Hat<br>
> <br>
<br>
<br>
_______________________________________________<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>
</blockquote></div></blockquote></div>