Upgrade WildFly to 35.0.1.Final.

[rhusar]

No description provided.

[WolfgangHG]

@rhusar JFYI I think 5.1.0.Beta11 broke the "wildfly-remote" profile that I prefer to use for development. I filed https://issues.redhat.com/browse/WFARQ-207 - maybe this new version is simply not compatible to 35.0.x.

[rhusar]

@rhusar JFYI I think 5.1.0.Beta11 broke the "wildfly-remote" profile that I prefer to use for development. I filed https://issues.redhat.com/browse/WFARQ-207 - maybe this new version is simply not compatible to 35.0.x.

Interesting, had a quick look and the version of jboss-logging is old thus the problem when running with this profile. I don't see us changing the dependency tree in that profile, so looks like problem upstream indeed

mvn clean dependency:tree -Pwildfly-remote
...
[INFO] | | +- org.jboss.logging:jboss-logging:jar:3.4.3.Final:test

[rhusar]

OK this is problem in POM of wildfly-arquillian-common which depends on org.jboss.remotingjmx:remoting-jmx which bings in old version as transitive dependency.

[rhusar]

@WolfgangHG OK, submitted a PR with the fix: wildfly/wildfly-arquillian#550