This usage of WildFly Maven Plugin on QS Aggregator is only so we batch and invoke mvn wildfly:deploy on all QS, it does not affects any QS, which uses the version in its context. This should be removed once we have the basic runtime testing CI per Quickstart.

As for the plugin management in the parent, that means we are hiding there some pom.xml content that the user apps need, and thus should not happen any longer, any plugin that the user app needs should be managed in the app instead.