[jbosstools-issues] [JBoss JIRA] (JBIDE-16176) Wrong archetype id used to lookup stacks archetypes

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-16176:
---------------------------------------------

I +1'ed the fix but where are the unit tests ? we had such earlier on for stacks afaik.
                
> Wrong archetype id used to lookup stacks archetypes
> ---------------------------------------------------
>
>                 Key: JBIDE-16176
>                 URL: https://issues.jboss.org/browse/JBIDE-16176
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: common/jst/core
>    Affects Versions: 4.1.1.CR1
>            Reporter: Fred Bricon
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 4.1.1.Final
>
>
> In https://github.com/jbosstools/jbosstools-base/blob/f38a27f16f5a0d5b0b11b9eae72df130cbad2e0c/stacks/plugins/org.jboss.tools.stacks.core/src/org/jboss/tools/stacks/core/model/StacksUtil.java#L65, the test should be archetypeId.equals(a.getId())
> Latest stacks.yaml now has multiple archetypes with the same maven archetype id, but we're supposed to distinguish them via the stacks archetype  Id. As a result, JBDS 7.1 will get the archetypes destined for JBDS 7.0, having the same maven archetype id.

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