[jbosstools-issues] [JBoss JIRA] (JBIDE-18436) Central archetype versions should depend on selected runtime version

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006656#comment-13006656 ] 

Fred Bricon edited comment on JBIDE-18436 at 9/26/14 5:33 PM:
--------------------------------------------------------------

Proposed fix tries to match WTP runtime version to the Stacks runtime candidates version.

https://github.com/jbosstools/jbosstools-central/pull/295

WTP runtime version is inferred from ServerBeanLoader (looking at local manifest).
Remote runtimes version can not be determined via this method, though, so they would still be receive the default archetype version


was (Author: fbricon):
Proposed fix tries to match WTP runtime version to the Stacks runtime candidates version.

https://github.com/jbosstools/jbosstools-central/pull/295

> 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)