[ARCHETYPE-438] Remove support for specifying catalogs through direct URLs

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Component/s: Generator
• Environment: n/a
• Assignee: Robert Scholte
• Reporter: Anders Hammar
• Created: 15/May/13 04:20
• Updated: 20/May/17 09:18
• Resolved: 28/Jan/17 12:47

Description

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.

Issue Links

• breaks: ARCHETYPE-519 archetype:generate with specified remote archetypeCatalog falls back to internal catalog
• is depended upon by: ARCHETYPE-521 Cannot specify remote repository for generate project from archetype
• is related to: ARCHETYPE-439 Remove archetypeRepository param