[
https://issues.jboss.org/browse/JBIDE-18436?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-18436:
---------------------------------------------
I honestly thought we already did this since it was necessary very early on - and yes,
remote servers we won't be able to handle unless we add support for asking a running
server what version it is.
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
Priority: Critical
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)