For any of our archetypes that generate a project with repositiories/pluginRepositories pom sections that list JBoss Nexus, add maven central as well, listed before JBoss Nexus.

We need to list JBoss Nexus as a repository in any pom that includes provisioning WildFly as one of its build steps. This is because not all artifacts that are provisioned in a WildFly installation are obtainable from maven central.

But the large majority of artifacts are available in central, and in general maven central seems to have faster and more reliable repository infrastructure, so it should be the preferred option.

Per https://maven.apache.org/guides/mini/guide-multiple-repositories.html, section "Repository Order", assuming the user's own settings.xml doesn't say otherwise if the project pom lists JBoss Nexus but doesn't list maven central before it, then maven central will be lower priority than JBoss Nexus. (The instruction to use maven central repo at all comes from item 2.C, the "Super POM", which is essentially a base POM built into Maven itself.)