JPA tests fail on wildfly

[blabno]

cd jpa/criteria
mvn test -P wildfly-embedded-arquillian

java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
        at org.jboss.arquillian.container.impl.client.container.ContainerRegistryCreator.createRegistry(ContainerRegistryCreator.java:116)

[bartoszmajsak]

I'm afraid that's not the only one failing. I have a feeling the whole setup needs quite a bit of love, as it seems to me to be a bit of a shaky ground

[arjantijms]

What if you run against a remote Wildly (the project's default profile), and what if you run the tests from the root? (if needed comment out all modules except for the util and JPA in the main pom)

I personally never got [cd somemodule/] to work to be honest.

[blabno]

@arjantijms default Wildfly works both from top dir and cd jpa/criteria.

[blabno]

Ok, so the reason for this error is lack of arquillian.xml with wildfly qualifier:

<container qualifier="wildfly"></container>

[blabno]

This requirement was introduced in 5bb2f77

[blabno]

So either we add arquillian.xml with container with wildfly qualifier to each module
or we remove this line:

5bb2f77#diff-600376dffeb79835ede4a0b285078036R468

[blabno]

@johnament you've added that wildfly qualifier to global config when you were modifying jms-xa sample. I've tried running tests for it with your changes, but they fail so I have no idea how to test impact of reverting your change to global wildfly-embedded-arquillian profile.

[johnament]

I know the configuration is needed for the JMS stuff to work. I also know that when I made the change, it was based on some discussions we were having about trying to run a single container for the entire test suite. That proved to be not stable in both cloudbees and travis.

I would recommend making this the default config overall (standalone-full.xml) but will leave it up to other to decide since I'm not particularly active on this project right now.