[ https://issues.jboss.org/browse/JBDS-2997?page=com.atlassian.jira.plugin.... ] Fred Bricon edited comment on JBDS-2997 at 4/4/14 5:45 AM: ----------------------------------------------------------- WFK 2.5 archetypes don't show up in central because they're only added to EAP 6.2 in stacks.yaml In JBDS, all EAP 6.1+ servers have the same runtime type, org.jboss.ide.eclipse.as.runtime.eap.61. In JBoss Central, when we try to lookup archetypes matching an EAP 6.2 runtime, we use the WTP runtimeid, org.jboss.ide.eclipse.as.runtime.eap.61, and find several matching runtimes in stacks (6.1.0 and 6.2.0). We use the first one, 6.1.0, but it 's not configured to use WFK 2.5 archetypes, so they're not displayed in central https://github.com/jboss-jdf/jdf-stack/pull/39 adds the WFK 2.5 archetypes to EAP 6.1.0. In theory, there should be no reason why they'd be incompatible. was (Author: fbricon): WFK 2.5 archetypes don't show up in central because they're only added to EAP 6.2 In JBDS, all EAP 6.1+ servers have the same runtime type, org.jboss.ide.eclipse.as.runtime.eap.61. In JBoss Central, when we try to lookup archetypes matching an EAP 6.2 runtime, we use the WTP runtimeid, org.jboss.ide.eclipse.as.runtime.eap.61, and find several matching runtimes in stacks (6.1.0 and 6.2.0). We use the first one, 6.1.0, but it 's not configured to use WFK 2.5 archetypes, so they're not displayed in central https://github.com/jboss-jdf/jdf-stack/pull/39 adds the WFK 2.5 archetypes to EAP 6.1.0. In theory, there should be no reason why they'd be incompatible. -- 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