[
https://issues.apache.org/jira/browse/ARCHETYPE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15844049#comment-15844049
]
Hudson commented on ARCHETYPE-438:
----------------------------------
SUCCESS: Integrated in Jenkins build maven-archetype-m3 #251 (See
[https://builds.apache.org/job/maven-archetype-m3/251/])
[ARCHETYPE-438] Remove support for specifying catalogs through direct
(rfscholte: rev 93318023353fd1a90f9a0b554dffd90f6de0cb56)
* (edit)
archetype-common/src/main/java/org/apache/maven/archetype/DefaultArchetypeManager.java
* (edit)
maven-archetype-plugin/src/main/java/org/apache/maven/archetype/ui/generation/DefaultArchetypeSelector.java
* (edit)
maven-archetype-plugin/src/main/java/org/apache/maven/archetype/mojos/CreateProjectFromArchetypeMojo.java
* (edit)
archetype-common/src/main/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSource.java
* (edit)
archetype-common/src/main/java/org/apache/maven/archetype/source/LocalCatalogArchetypeDataSource.java
* (edit)
archetype-common/src/main/java/org/apache/maven/archetype/ArchetypeManager.java
* (edit)
archetype-common/src/main/java/org/apache/maven/archetype/source/InternalCatalogArchetypeDataSource.java
* (edit)
archetype-common/src/test/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSourceTest.java
* (edit)
archetype-common/src/main/java/org/apache/maven/archetype/source/ArchetypeDataSource.java
> Remove support for specifying catalogs through direct URLs
> ----------------------------------------------------------
>
> Key: ARCHETYPE-438
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-438
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Generator
> Environment: n/a
> Reporter: Anders Hammar
> Assignee: Robert Scholte
> Fix For: 3.0.0
>
>
> It is currently possible to specify a archetype catalog through a file: or
> http: URL (via the archetypeCatalog param). This adds the possibility to go
> outside of the configured Maven infrastructure which causes problems and
> unpredicted side-effects.
> I strongly argue that the plugin should work with the Maven settings and
> infrastructure in place and not allow for going outside of this. For example,
> in a setup where there is a Maven repo manager in place it should always be
> used and the user should not be allowed to side-step it through the support
> of the plugin. If an additional source should be used, it should be setup
> properly in the Maven configuration/infrastructure.
> I also believe the current support is a legacy from the old days when the
> catalog at central was not complete, but one had to used additional catalogs
> in the Internet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
