Bug 1390158 - FIS archetype catalog should point to a FIS-specific one
Summary: FIS archetype catalog should point to a FIS-specific one
Keywords:
Status: NEW
Alias: None
Product: Red Hat xPaaS
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: nshendye
QA Contact: Marek Schmidt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-31 11:01 UTC by Marek Schmidt
Modified: 2022-01-14 13:13 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.