<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Plugin is used by EAP maven repo build to generate eap-runtime
bom eg [1] based on the feature packs dependency tree.</p>
<p>Relevant configuration is <a moz-do-not-send="true"
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">[2]</a>
<br>
</p>
<br>
Petr<br>
<br>
[1] <a moz-do-not-send="true"
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">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>
<div class="moz-cite-prefix"><br>
[2] <a moz-do-not-send="true"
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">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>
</div>
<blockquote type="cite"
cite="mid:CAPhbRDYpJVgmwHC08PHtrGH+tUzzigu6zX6Ht-OXZqfymSNFVA@mail.gmail.com">
<div dir="ltr">Hi Paul and Petr,
<div><br>
</div>
<div>Do you know of any uses of this plugin we could learn from?</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Brian</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, May 5, 2018 at 4:25 AM, Kabir
Khan <span dir="ltr"><<a href="mailto:kkhan@redhat.com"
target="_blank" moz-do-not-send="true">kkhan@redhat.com</a>></span>
wrote:<br>
<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" moz-do-not-send="true">https://github.com/jboss/bom-<wbr>builder-maven-plugin</a>
can be used? I've not played with it<br>
<div class="HOEnZb">
<div class="h5"><br>
> On 4 May 2018, at 22:11, David Lloyd <<a
href="mailto:david.lloyd@redhat.com"
moz-do-not-send="true">david.lloyd@redhat.com</a>>
wrote:<br>
> <br>
> I've created <a
href="https://issues.jboss.org/browse/WFLY-10330"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://issues.jboss.org/<wbr>browse/WFLY-10330</a>
and<br>
> <a
href="https://issues.jboss.org/browse/WFCORE-3803"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://issues.jboss.org/<wbr>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"
moz-do-not-send="true">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"
moz-do-not-send="true">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>
>>> ______________________________<wbr>_________________<br>
>>> wildfly-dev mailing list<br>
>>> <a
href="mailto:wildfly-dev@lists.jboss.org"
moz-do-not-send="true">wildfly-dev@lists.jboss.org</a><br>
>>> <a
href="https://lists.jboss.org/mailman/listinfo/wildfly-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
> <br>
> <br>
> <br>
> -- <br>
> - DML<br>
> ______________________________<wbr>_________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org"
moz-do-not-send="true">wildfly-dev@lists.jboss.org</a><br>
> <a
href="https://lists.jboss.org/mailman/listinfo/wildfly-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org"
moz-do-not-send="true">wildfly-dev@lists.jboss.org</a><br>
<a
href="https://lists.jboss.org/mailman/listinfo/wildfly-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Brian Stansberry
<div>Manager, Senior Principal Software Engineer</div>
<div>Red Hat</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>