[jbosstools-issues] [JBoss JIRA] (JBIDE-16577) Remove remote JBoss Archetype catalog

[Rob Cernich (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944736#comment-12944736 ] 

Rob Cernich commented on JBIDE-16577:
-------------------------------------

Hey [~fbricon],

Sounds good to me.  SwitchYard was only relying on the index to resolve available dependency versions and does not currently use archetypes.  That said, this functionality has been removed from SwitchYard and we now rely on server definitions to provide the "correct" versions for maven projects.

Thanks for looking into this though.

Rob
                
> Remove remote JBoss Archetype catalog
> -------------------------------------
>
>                 Key: JBIDE-16577
>                 URL: https://issues.jboss.org/browse/JBIDE-16577
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 4.1.1.Final
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: 4.1.2.CR1
>
>
> 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. [~rcernich] WDYT?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira