[
https://issues.jboss.org/browse/JBIDE-16292?page=com.atlassian.jira.plugi...
]
Radim Hopp commented on JBIDE-16292:
------------------------------------
{quote}
In practice, the current stacks.yaml file doesn't currently provide ways to test the
fix (unit tests do), We'll have to wait for WFK 2.5 archetypes to be added to EAP 6.2
to see it work
{quote}
[~fbricon] So basically we have to wait for WFK 2.5 to release GA to verify it?
Need to restore ability to select specific archetype version per
runtime in Central
-----------------------------------------------------------------------------------
Key: JBIDE-16292
URL:
https://issues.jboss.org/browse/JBIDE-16292
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, project-examples
Affects Versions: 4.1.1.Final
Reporter: Fred Bricon
Assignee: Fred Bricon
Priority: Critical
Fix For: 4.1.2.CR1
The changes done in JBIDE-15645 introduced a regression in the way archetypes are
selected.
Basically, we can get different archetype versions depending on the EE version of the
runtime (web/full-ee6 vs web/full-ee7) but we lost the ability to pick a different
archetype version between 2 different runtimes of the same product and same EE level (eg.
EAP 6.1 vs EAP 6.2)
As a consequence, archetype versions designed to run on EAP 6.2 will be selected when
EAP 6.1 is selected in the project wizard.
Hopefully EAP 6.2 archetypes will still be able to run on EAP 6.1 so that shouldn't
be a problem, but we should fix that for the next minor release.
--
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