[jbosstools-dev] Mechanism for deciding which archetype will be used for target runtime.

[Max Rydahl Andersen]

On 6 Oct 2015, at 13:01, Radim Hopp wrote:

> Hi,
> I guess, that the main mechanism for deciding which archetype will be 
> used
> for which server runtime is stacks.yaml, but what about runtimes, 
> which are
> not in stacks.yaml yet?
>

mainly a question for Fred and Rob.

> For example now, when I try to create EAR project with target runtime 
> EAP7
> (EAP7 is not yet in stacks.yaml), it
> creates 
> org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final
> (archetype for JBossAS 7) and this doesn't seem right.

Which one would you expect when unknown ? we fall back to the latest 
working version afaik.

> Another example: EAR project with target runtime WFLY9
> -> 
> rg.wildfly.archetype:wildfly-javaee7-webapp-ear-archetype:8.2.0.Final.
> This looks pretty ok, as this is WFLY8.2 archetype and WFLY9 
> archetypes are
> not released yet.

Neither is EAP7.

When you use WF9 you use WF8 adapter right ? thus that will give you WF8 
examples.

Seems like stacks.yml need some updates. Fred/Rob ?
/max
http://about.me/maxandersen