Following HSEARCH-2988, most of the build already works without any specific Maven configuration from the user, but there are still a gotchas:
the WildFly server, when it starts, will download artifacts from Maven to complete the "thin" modules we provisioned using the wildfly-provisioning-maven-plugin. And unfortunately the server is not aware of the Maven configuration of our build, so it doesn't know about our custom local repository (if any) or about the hard-coded JBoss Nexus repository in our POM.
Karaf, in OSGi integration tests, faces the same issue regarding the local repository.
We should find a way to configure this.