[jbosstools-issues] [JBoss JIRA] (JBDS-3579) Fuse archetype catalog cannot be added with JBDS 9

[Fred Bricon (JIRA)]

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

Fred Bricon edited comment on JBDS-3579 at 1/5/16 11:32 AM:
------------------------------------------------------------

When querying the catalog from CLI, an exception is thrown in RemoteCatalogArchetypeDataSource.getArchetypeCatalog(properties) (as expected since archetype-catalog.xml was appended to the url) :
{quote}
 org.apache.maven.wagon.ResourceDoesNotExistException: File: https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archetypes/archetypes-catalog/2.2.0.redhat-079/archetypes-catalog-2.2.0.redhat-079-archetype-catalog.xml/archetype-catalog.xml , ReasonPhrase:Not Found. 
{quote}
That Exception is caught in the outer catch block (https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=blob;f=archetype-common/src/main/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSource.java;h=1e5838fd60021ae5e07daa9c6176dfbef856f5b0;hb=HEAD#l81) which  then falls back on using the actual catalog url and succeeds.

In m2e 1.6+ however, a different transport mechanism (OkHttp) is used. The transport connects to the url, then proceeds to try to parse the content of the temporary file supposed to hold the catalog. Parsing fails and an ArchetypeDataSourceException is thrown, which is intercepted and rethrown in https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=blob;f=archetype-common/src/main/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSource.java;h=1e5838fd60021ae5e07daa9c6176dfbef856f5b0;hb=HEAD#l78 instead.


was (Author: fbricon):
When querying the catalog from CLI, an exception is thrown in RemoteCatalogArchetypeDataSource.getArchetypeCatalog(properties) (as expected since archetype-catalog.xml was appended to the url) :
{quote}
 org.apache.maven.wagon.ResourceDoesNotExistException: File: https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archetypes/archetypes-catalog/2.2.0.redhat-079/archetypes-catalog-2.2.0.redhat-079-archetype-catalog.xml/archetype-catalog.xml , ReasonPhrase:Not Found. 
{quote}
RemoteCatalogArchetypeDataSource.getArchetypeCatalog(properties). That Exception is caught in the outer catch block (https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=blob;f=archetype-common/src/main/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSource.java;h=1e5838fd60021ae5e07daa9c6176dfbef856f5b0;hb=HEAD#l81) which  then falls back on using the actual catalog url and succeeds.

In m2e 1.6+ however, a different transport mechanism (OkHttp) is used. The transport connects to the url, then proceeds to try to parse the content of the temporary file supposed to hold the catalog. Parsing fails and an ArchetypeDataSourceException is thrown, which is intercepted and rethrown in https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=blob;f=archetype-common/src/main/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSource.java;h=1e5838fd60021ae5e07daa9c6176dfbef856f5b0;hb=HEAD#l78 instead.

> Fuse archetype catalog cannot be added with JBDS 9
> --------------------------------------------------
>
>                 Key: JBDS-3579
>                 URL: https://issues.jboss.org/browse/JBDS-3579
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: maven
>    Affects Versions: 9.0.0.GA
>            Reporter: Keith Babo
>            Assignee: Fred Bricon
>
> When adding the Fuse Integration Services archetype catalog to JBDS 9, the IDE reports that the catalog is empty.  This works in Eclipse and I've heard reports that it also works in earlier versions of JBDS (although I have not confirmed this personally).  
> Archetype catalog in question:
> https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archetypes/archetypes-catalog/2.2.0.redhat-079/archetypes-catalog-2.2.0.redhat-079-archetype-catalog.xml
> Steps to reproduce:
> - Preferences -> Maven -> Archetypes -> Add Remote Catalog
> - Add URL above for Catalog File
> - Click Verify ...  and you get the message "Remote catalog is empty"
> - Click Finish and try to use the catalog from the New Maven Project wizard and the message is "No archetypes available for this catalog."
> Impact here is that Fuse customers looking to use Fuse on OpenShift cannot use JBDS to create new projects using our Maven archetypes (the primary means of getting started).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)