]
Radim Hopp closed JBIDE-12217.
------------------------------
Verified in JBT 3.3.0 and JBT 4.0.0.Alpha1b
Make sure all archetypes in JBoss Central point at releases in Maven
Central
----------------------------------------------------------------------------
Key: JBIDE-12217
URL:
https://issues.jboss.org/browse/JBIDE-12217
Project: Tools (JBoss Tools)
Issue Type: Task
Components: central, project-examples
Affects Versions: 3.3.0.CR1
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 3.3.0.Final
Currently, we have aerogear, richfaces, javaee web and javaee ear pointing at forked
archetypes stored under
http://anonsvn.jboss.org/repos/jbosstools/workspace/fred/repositories/sna...
This is acceptable while we're doing milestones and all, but once JBT/JBDS are
released, the archetypes need to be picked from either Maven Central or JBoss Nexus, so as
to prevent issues with users mirroring all repository requests to a maven repository
manager
So, once the folowing commits are merged upstream, we should definitely point at the
corresponding releases :
* aerogear/HTML5 :
https://github.com/aerogear/as-archetypes/commit/614330ee9da67b6e244aaae6...
* richfaces :
https://github.com/richfaces/archetypes/commit/14308e75
* javaee web/ear :
https://github.com/fbricon/archetypes/commit/ee90b6377b0a34cb2219e2e56ee3...
--
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: