[wildfly-dev] How "optional" should the NoSQL integration be for WildFly...

Scott Marlow smarlow at redhat.com
Mon Sep 12 10:31:55 EDT 2016


Hi,

I'm thinking that the NoSQL unit tests should be optional, since most 
WildFly developers won't have access to a local NoSQL database server. 
Currently, to run the unit tests, you have to define "nosql-tests" (e.g. 
./integration-tests.sh -Dnosql-tests).

As we work towards our first (NoSQL integration) pull requests for 
WildFly master (and some small wildfly-core changes to the Phase class), 
does anything else need to be optional?

Currently we are building WildFly to include the NoSQL driver artifacts, 
for the specific versions of the drivers that we support.  We also allow 
other versions of the NoSQL drivers to be brought into WildFly, as long 
as they are (API) compatible with the version that we (loosely) 
integrate with.

Thanks for the feedback!

Scott


More information about the wildfly-dev mailing list