[
https://issues.jboss.org/browse/JBIDE-18436?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-18436:
-------------------------------------
When no runtime is selected, the default archetype version is used (with old BOMs), as it
doesn't depend on having the redhat maven repo defined in your settings.xml. More
recent versions of the archetypes are linked to specific EAP versions in stacks.yaml but
depend on the maven redhat repo.
Anyways, whichever EAP >= 6.1 runtime is used, the same (old) archetype version is
used, which is wrong.
The problem is caused by EAP 6.1, 6.2, 6.3 having the same WP runtime id, so we look for
the archetypes matching that id in stacks.yaml. The first runtime found is always
returned.
We need to be able to better match WTP runtime versions to their Stacks sibling
Central archetype versions should depend on selected runtime version
--------------------------------------------------------------------
Key: JBIDE-18436
URL:
https://issues.jboss.org/browse/JBIDE-18436
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.2.0.CR1
Environment: JBDS 8 CR1, Fedora 20
Reporter: Vineet Reynolds
Assignee: Fred Bricon
Fix For: 4.2.0.CR2
A newly created project using the "Java EE Web Project" in JBoss Central, uses
the {{org.jboss.bom:jboss-javaee-6.0-with-tools:1.0.4.Final-redhat-4}} and
{{org.jboss.bom:jboss-javaee-6.0-with-hibernate:1.0.4.Final-redhat-4}} BOMs in the
{{dependencyManagement}} section.
These are the older versions. It should instead be using the BOMs from the
{{org.jboss.bom.wfk}} and {{org.jboss.bom.eap}} groupIds instead.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)