[jbosstools-issues] [JBoss JIRA] (JBIDE-19030) Creation of new RichFaces project results in outdated archetype
[
https://issues.jboss.org/browse/JBIDE-19030?page=com.atlassian.jira.plugi...
]
Rafael Benevides commented on JBIDE-19030:
------------------------------------------
I realized that when I select EAP as Target runtime, it uses
org.jboss.archetype.wfk:richfaces-archetype-kitchensink:2.6.0.Final but
org.richfaces.archetypes:richfaces-archetype-kitchensink:4.2.3.Final-2 is used when I
select Wildfly.
Apparently JBDS isn't using the association from Runtime->Archetype as describe in
this line as example:
https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.y...
Anyway, the GAV org.richfaces.archetypes:richfaces-archetype-kitchensink:4.2.3.Final-2
appears on JBoss AS 7 runtime:
https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.y...
I hope these information helps the diagnostics because Stacks' Runtime->Archetype
relationship isn't being used at all.
Creation of new RichFaces project results in outdated archetype
---------------------------------------------------------------
Key: JBIDE-19030
URL: https://issues.jboss.org/browse/JBIDE-19030
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: project-examples
Affects Versions: 4.2.1.Final
Reporter: Matej Novotny
Assignee: Fred Bricon
Priority: Minor
Fix For: 4.3.x
In JBDS one can create RichFaces project via:
* File -> New -> Other -> RichFaces Project
This results in choosing kitchensink archetype for version 4.2.3 which is outdated.
There were some major changes to RichFaces beggining with version 4.5 so it would be nice
if JBDS could make use of any 4.5.x.Final version artifact instead.
Note: Latest archetype version is 4.5.1.Final and 4.5.2.Final is being staged at the
moment, so one of these two should be used I guess.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)