The JBoss remote archetype catalog was added with JBIDE-12094 to mitigate the loss of functionality caused by the removal of the JBoss nexus index (which caused JBIDE-12066)

Problem is, m2e tries to check the origin of a given archetype several (3 minimum) times during the creation process. It tries to lookup any selected archetype in all remote repositories in order to get the matching remote url if possible.

Problem is, JBoss Nexus is super super slow. Each lookup takes between 5 and 10 seconds (or more!). Given most archetypes come from Maven central this is a waste of time. When removed, creating any project from either JBoss Central or the Maven Wizard becomes much, much, much faster.

I have some work in progress to fix the dubious lookup logic in m2e but that won't be available before next june.

I believe even switchyard archetypes are now synch'ed to Maven central so the JBoss Archetype Catalog is not relevant anymore. I propose we remove it from the JBoss Maven Integration plugin. rcernich1 WDYT?