Hi.

So far, I have not been successfuly having the wildfly maven plugin behave as the standalone.bat script, and use it to startup any standalone server whose base dir is not the "standalone" base dir folder itself.

I believe the maven plugin is forcincing the convention that the stanadlone base dire has to be the standalone folder withing the wildfly home.

Here is an example.
If I am located at my WILDFLY_HOME\bin, I can trigger the following command line call to start up the appropriate standlone base dir with the appropriate configuration.

standalone.bat --server-config=standalone-empty.xml -Djboss.server.base.dir=C:\dev\Widlfly10\wildfly-10.0.0.Final\standalone-cli

On the other hand, If I were to try to the same thing using the maven plugin, I would be forced to run a "dirty command" (look at the relative path I am doing to access the configuration file) such as the following:

mvn org.wildfly.plugins:wildfly-maven-plugin:1.2.0.Alpha5:start -Dwildfly.server.type=STANDALONE -Djboss-as.home=C:\dev\Widlfly10\wildfly-10.0.0.Final -Dwildfly.serverArgs="-Djboss.server.base.dir=C:/dev/Widlfly10/wildfly-10.0.0.Final/standalone-cli" -Dwildfly.serverConfig=../../standalone-cli/configuration/standalone-empty.xml

The server starts up, but I can clearly see in jvisualvm that the base dir continues to be standalone folder.

However, if I play with the value I am setting on the -Djboss.server.base.dir= and I write the value something that is an invalid path, then I correctly get an error telling me that my folder is invalid.

This problem is also explained on the following stack over flow thread.
https://stackoverflow.com/questions/44654819/wildfly-maven-plugin-is-there-a-way-to-specify-the-jboss-server-base-dir

Am I making some sort of mistake on my configuration?
Or is there a bug in the plugin and a fix should be added to ensure that asking the pluging to start a standalone server with a different base directory is working properly?

My Kindest regards.