use mvn org.wildfly.plugins:wildfly-maven-plugin:5.1.2.Final:dev -Djboss-as.home="C:\\work application-servers wildfly-32.0.1.Final-avedia" change pom to add on the plugins tag under build tag the following <plugin> <groupId> org.wildfly.plugins </groupId> <artifactId> wildfly-maven-plugin </artifactId> <version> 5.1.2.Final </version> <configuration> <jbossHome> C:\\work\\application-servers\\wildfly-32.0.1.Final-avedia </jbossHome> </configuration> </plugin> according to documentation this should look at a local folder where wildfly is already available instead of downloading a new version, the result is an error stating  JBOSS_HOME 'C:\work\fusion-wildfly-service\target\server' is not a valid directory the path is an example on my use case but as you can see the path I pass with -D argument jboss-as.home or setting JBOSS_HOME env variable or using it on the plugin configuration on pom.xml is not read