Bug 1390158

Summary: FIS archetype catalog should point to a FIS-specific one
Product: Red Hat xPaaS Reporter: Marek Schmidt <maschmid>
Component: DocumentationAssignee: nshendye
Status: NEW --- QA Contact: Marek Schmidt <maschmid>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecified   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marek Schmidt 2016-10-31 11:01:35 UTC 
Description of problem:

https://access.redhat.com/documentation/en/red-hat-xpaas/0/paged/red-hat-xpaas-fuse-integration-services-image/chapter-3-get-started

contains the following command:

$ mvn archetype:generate \
  -DarchetypeCatalog=https://repo.fusesource.com/nexus/content/groups/public/archetype-catalog.xml \
  -DarchetypeGroupId=io.fabric8.archetypes \
  -DarchetypeVersion=2.2.0.redhat-079 \
  -DarchetypeArtifactId=<archetype-name>


While that works OK, the mentioned catalog also provides archetypes that are not FIS-specific, which is confusing.

The command should instead use

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

as the archetypeCatalog, as that only contains FIS archetypes.

Version-Release number of selected component (if applicable):

0