Re: [wildfly-dev] Wildfly 9 BOM changes
Hey Thomas,
yes, boms ware modifed to have scope provided, as given the feedback on
forums lots of folks had problems with
bundling the API jars with their application, which resulted in lots of
deployment problems.
The testing on other hand results in problems you have, which are quite
easily fixed if you change the scope of dependency
when you are defining deps for your test modules.
Question is what is more common problem, one or another. It is hard to
choose what to cater to in this case.
I think that best thing do here is to update our quickstarts that reflect
how to work with newer boms.
Maybe someone else has better idea?
--
tomaz
On Mon, Jun 29, 2015 at 6:04 PM, Thomas Segismont <tsegismo(a)redhat.com>
wrote:
Hi everyone,
While working on upgrading Hawkular to Wildfly 9 CR2, we have noticed
that the Wildfly BOM now declares provided scope for some dependencies.
I guess the goal is to help users which forget to set the provided scope
in their POM to end up with all the libraries in their WAR.
On the other hand, if you use some libraries in your tests, then
dependency resolution can be broken. For example, if you add
org.jboss.resteasy::resteasy-client in test scope, your tests fail due
to a missing class from commons-io, because commons-io should be
resolved as a transitive dependency of
org.jboss.resteasy::resteasy-jaxrs, but it's now in scope provided,
instead of test.
Have you considered this use case? Are there other motivations than
helping Maven beginners?
Best regards,
Thomas
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Attachments:
- attachment.html (text/html — 2.4 KB)