Just an additional thought. This is already possible with the jboss-as-maven-plugin. The one thing we could add to the plugin would be to allow for wildcard files which could be beneficial anyway.

Example*:
            <plugin>
                <groupId>org.jboss.as.plugins</groupId>
                <artifactId>jboss-as-maven-plugin</artifactId>
                <version>${version.jboss.maven.plugin}</version>
                <inherited>true</inherited>
                <configuration>
                    <skip>true</skip>
                </configuration>
                <executions>
                    <execution>
                        <id>start-server</id>
                        <phase>process-resources</phase>
                        <goals>
                            <goal>start</goal>
                        </goals>
                        <configuration>
                            <jboss-as-version>${version.org.jboss.as.dist}</jboss-as-version>
                        </configuration>
                    </execution>
                    <execution>
                        <id>validate-scripts</id>
                        <phase>process-resources</phase>
                        <goals>
                            <goal>execute-commands</goal>
                        </goals>
                        <configuration>
                            <execute-commands>
                                <scripts>
                                    <script>${project.basedir}/deltaspike-helloworld-jms/configure-jms.cli</script>
                                    <script>${project.basedir}/deltaspike-helloworld-jms/remove-jms.cli</script>
                                </scripts>
                            </execute-commands>
                        </configuration>
                    </execution>
                    <execution>
                        <id>shutdown-server</id>
                        <phase>process-resources</phase>
                        <goals>
                            <goal>shutdown</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

* Note: This uses the 7.4.Final version of the plugin

On 05/14/2013 09:52 AM, James R. Perkins wrote:

I started a conversion on a PR, https://github.com/jboss-jdf/jboss-as-quickstart/pull/500#issuecomment-17850009, about creating a maven plugin to validate the CLI scripts in the Quickstarts.

Pete suggested this might be a good thing for Arquillian to support. I did find and arquillian-maven plugin [1], but it looks like it hasn't been updated in a while. I'm also not sure if the ARQ API can handle scripts. I don't mind helping update the plugin if that seems like a viable solution. Also I don't mind adding support to the WildFly ARQ to allow for scripts.

If anyone has any thoughts or opinions on this feel free to express them. I'm not sure if we even want to do the validation, but it does seem it would be useful. Especially as quickstart targeted servers change.

[1]: https://github.com/arquillian/arquillian-maven
-- 
James R. Perkins
JBoss by Red Hat

-- 
James R. Perkins
JBoss by Red Hat