January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19030) Creation of new RichFaces project results in outdated archetype

by Rafael Benevides (JIRA)

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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19029) Error: "Attribute name is not allowed to appear in element sub-deployment" in two Seam examples

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19029?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19029: ----------------------------------- Fix Version/s: 4.2.3.Final 4.3.0.Alpha1 > Error: "Attribute name is not allowed to appear in element sub-deployment" in two Seam examples > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19029 > URL: https://issues.jboss.org/browse/JBIDE-19029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Environment: JBDS 8.0.1.GA > Reporter: Matous Jobanek > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > When the projects > * mail-ear from the Seam example mail \[1\] > * tasks-ear from the Seam example tasks \[2\] > are imported into JBDS the error > {panel} > Attribute 'name' is not allowed to appear in element 'sub-deployment' > {panel} > will be shown for the file jboss-deployment-structure.xml. > It is caused by the bug in _jboss-deployment-structure-1_0.xsd_; see AS7-1345 > This bug should be IMHO ignored and the error shouldn't be shown. > \[1\] https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/mail > \[2\] https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/tasks -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19029) Error: "Attribute name is not allowed to appear in element sub-deployment" in two Seam examples

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19029?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19029: -------------------------------------- Assignee: Viacheslav Kabanovich Slava, could you please take a look? > Error: "Attribute name is not allowed to appear in element sub-deployment" in two Seam examples > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19029 > URL: https://issues.jboss.org/browse/JBIDE-19029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Environment: JBDS 8.0.1.GA > Reporter: Matous Jobanek > Assignee: Viacheslav Kabanovich > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > When the projects > * mail-ear from the Seam example mail \[1\] > * tasks-ear from the Seam example tasks \[2\] > are imported into JBDS the error > {panel} > Attribute 'name' is not allowed to appear in element 'sub-deployment' > {panel} > will be shown for the file jboss-deployment-structure.xml. > It is caused by the bug in _jboss-deployment-structure-1_0.xsd_; see AS7-1345 > This bug should be IMHO ignored and the error shouldn't be shown. > \[1\] https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/mail > \[2\] https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/tasks -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19030) Creation of new RichFaces project results in outdated archetype

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19030?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19030: ------------------------------------- The archetype version is defined upstream in https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.yaml. [~rafabene] should be able to help, hopefully. > 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)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19029) Error: "Attribute name is not allowed to appear in element sub-deployment" in two Seam examples

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19029?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19029: ----------------------------------- Component/s: server upstream > Error: "Attribute name is not allowed to appear in element sub-deployment" in two Seam examples > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19029 > URL: https://issues.jboss.org/browse/JBIDE-19029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Environment: JBDS 8.0.1.GA > Reporter: Matous Jobanek > > When the projects > * mail-ear from the Seam example mail \[1\] > * tasks-ear from the Seam example tasks \[2\] > are imported into JBDS the error > {panel} > Attribute 'name' is not allowed to appear in element 'sub-deployment' > {panel} > will be shown for the file jboss-deployment-structure.xml. > It is caused by the bug in _jboss-deployment-structure-1_0.xsd_; see AS7-1345 > This bug should be IMHO ignored and the error shouldn't be shown. > \[1\] https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/mail > \[2\] https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/tasks -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19030) Creation of new RichFaces project results in outdated archetype

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19030?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19030: ----------------------------------- Assignee: Fred Bricon (was: Snjezana Peco) > 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)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19031) Update stacks.yaml with latest RichFaces archetype

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19031?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19031: ----------------------------------- Assignee: (was: Snjezana Peco) > Update stacks.yaml with latest RichFaces archetype > -------------------------------------------------- > > Key: JBIDE-19031 > URL: https://issues.jboss.org/browse/JBIDE-19031 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: project-examples > Reporter: Matej Novotny > Priority: Minor > > 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)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19031) Update stacks.yaml with latest RichFaces archetype

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-19031: ----------------------------------- Summary: Update stacks.yaml with latest RichFaces archetype Key: JBIDE-19031 URL: https://issues.jboss.org/browse/JBIDE-19031 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: project-examples Affects Versions: 4.2.1.Final Reporter: Matej Novotny Assignee: Snjezana Peco 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)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19030) Creation of new RichFaces project results in outdated archetype

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19030?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19030: -------------------------------------- Assignee: Snjezana Peco > 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: Snjezana Peco > 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)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19030) Creation of new RichFaces project results in outdated archetype

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19030?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19030: ----------------------------------- Fix Version/s: 4.3.x > 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: Snjezana Peco > 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)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015