[ 
https://issues.apache.org/jira/browse/ARCHETYPE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated ARCHETYPE-655:
--------------------------------------
    Description: 
Currently the {{RemoteCatalogArchetypeDataSource}} relies on Wagon API to 
download the catalog from a Maven repository 
([https://github.com/apache/maven-archetype/blob/3a2b725198c3823fd5d7e9f88b665b2e4515a202/archetype-common/src/main/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSource.java#L127-L149]).
 

Instead the Maven Resolver API should be used directly. At the same time some 
more flexibility with regards to repository ids would be beneficial (in order 
to support multiple custom catalogs or to reuse existing repository/server 
sections in the {{{}settings.xml{}}}). In the best case even merging catalog 
XMLs from multiple repos (with deduplication) should be supported.

 

  was:
Currently the {{RemoteCatalogArchetypeDataSource}} relies on Wagon API to 
download the catalog from a Maven repository 
(https://github.com/apache/maven-archetype/blob/3a2b725198c3823fd5d7e9f88b665b2e4515a202/archetype-common/src/main/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSource.java#L127-L149).
 

Instead the Maven Resolver API should be used directly. At the same time some 
more flexibility with regards to repository ids would be beneficial (in order 
to support multiple custom catalogs or to reuse existing repository/server 
sections in the {{{}settings.xml{}}})

 


> Get rid of Wagon API to download catalogs
> -----------------------------------------
>
>                 Key: ARCHETYPE-655
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-655
>             Project: Maven Archetype
>          Issue Type: Improvement
>            Reporter: Konrad Windszus
>            Priority: Major
>
> Currently the {{RemoteCatalogArchetypeDataSource}} relies on Wagon API to 
> download the catalog from a Maven repository 
> ([https://github.com/apache/maven-archetype/blob/3a2b725198c3823fd5d7e9f88b665b2e4515a202/archetype-common/src/main/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSource.java#L127-L149]).
>  
> Instead the Maven Resolver API should be used directly. At the same time some 
> more flexibility with regards to repository ids would be beneficial (in order 
> to support multiple custom catalogs or to reuse existing repository/server 
> sections in the {{{}settings.xml{}}}). In the best case even merging catalog 
> XMLs from multiple repos (with deduplication) should be supported.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to