[
https://issues.jboss.org/browse/JDF-112?page=com.atlassian.jira.plugin.sy...
]
Fred Bricon updated JDF-112:
----------------------------
Description:
We need to be able to define a non-default repository hosting the archetypes.
Use case : a new archetype (not-sync with central) is used, we need to know where to get
it from (jboss nexus repo).
An optional repositoryUrl could be set on the Archetype model AND on ArchetypeVersion :
In order to d/l an archetype, we check if it has a repositoryUrl, if it doesn't we
check if its parent archetype has one. If none is defined, we assume it comes from Maven
Central.
was:
We need to be able to define a non-default repository hosting the archetypes.
Use case : a new archetype (not-sync with central) is used, we need to know where to get
it from (jboss nexus repo).
An optional repositoryUrl could be set on the Archetype model AND on ArchetypeVersion :
In order to d/l an archetype, we check if it has a repositoryUrl, if it doesn't we
check if its parent archetype has one. If none is define, we assume it comes from Maven
Central.
Add repository url on Archetype / ArchetypeVersion
--------------------------------------------------
Key: JDF-112
URL:
https://issues.jboss.org/browse/JDF-112
Project: JBoss Developer Framework
Issue Type: Feature Request
Components: stacks
Reporter: Fred Bricon
Assignee: Rafael Benevides
We need to be able to define a non-default repository hosting the archetypes.
Use case : a new archetype (not-sync with central) is used, we need to know where to get
it from (jboss nexus repo).
An optional repositoryUrl could be set on the Archetype model AND on ArchetypeVersion :
In order to d/l an archetype, we check if it has a repositoryUrl, if it doesn't we
check if its parent archetype has one. If none is defined, we assume it comes from Maven
Central.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira