Yes, your application deployed without errors. We are working on fixing this erroneous error in XNIO.
This is the command-line public API looking for the JBOSS_HOME directory. This error can be ignored.
JBoss Modules used to require the log manager be passed via the command line but switched to using a service loader approach. The plugin no longer use the old method.
Workaround to this issue is to specify the log manager via the plugin's jvmArgs configuration.
... <jvmArgs> <!-- Below should be your default jboss jvm args --> -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 <!-- From this point on is the workaround --> <!-- ${downloadedJbossDir} should point to your downloaded jboss --> <!-- The jar file name should match your jboss version --> -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:${downloadedJbossDir}/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.0.GA.jar -Xbootclasspath/p:${downloadedJbossDir}/modules/org/jboss/logmanager/log4j/main/jboss-logmanager-log4j-1.0.0.GA.jar -Xbootclasspath/p:${downloadedJbossDir}/modules/org/apache/log4j/main/log4j-1.2.16.jar </jvmArgs> ...