<div dir="ltr"><div>Just an update on this, as we discussed it with Thomas on IRC.<br><br></div><div>Result are fixed boms that ware just released with version of 9.0.0.Final<br></div><div>that is also in sync with just released WildFly 9.0.0.Final deps.<br><br>--<br></div><div>tomaz<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 29, 2015 at 6:04 PM, Thomas Segismont <span dir="ltr"><<a href="mailto:tsegismo@redhat.com" target="_blank">tsegismo@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi everyone,<br>
<br>
While working on upgrading Hawkular to Wildfly 9 CR2, we have noticed<br>
that the Wildfly BOM now declares provided scope for some dependencies.<br>
<br>
I guess the goal is to help users which forget to set the provided scope<br>
in their POM to end up with all the libraries in their WAR.<br>
<br>
On the other hand, if you use some libraries in your tests, then<br>
dependency resolution can be broken. For example, if you add<br>
org.jboss.resteasy::resteasy-client in test scope, your tests fail due<br>
to a missing class from commons-io, because commons-io should be<br>
resolved as a transitive dependency of<br>
org.jboss.resteasy::resteasy-jaxrs, but it's now in scope provided,<br>
instead of test.<br>
<br>
Have you considered this use case? Are there other motivations than<br>
helping Maven beginners?<br>
<br>
Best regards,<br>
Thomas<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">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><br></div>