January 2015 - jbosstools-issues - Jboss List Archives

[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: ----------------------------------- Component/s: project-examples > 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 > > 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: ----------------------------------- Priority: Minor (was: Major) > 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 > 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-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: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-19030 (was: JBDS-3313) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Affects Version/s: 4.2.1.Final (was: 8.0.1.GA) Docs QE Status: (was: NEW) Target Release: (was: 8.1.0.GA) > 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 > Affects Versions: 4.2.1.Final > Reporter: Matej Novotny > > 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-19023) CDI validation cannot find beans in src/test to be used for injection

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19023?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19023: ----------------------------------- Fix Version/s: (was: 4.2.3.Final) > CDI validation cannot find beans in src/test to be used for injection > --------------------------------------------------------------------- > > Key: JBIDE-19023 > URL: https://issues.jboss.org/browse/JBIDE-19023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Jason Porter > Assignee: Alexey Kazakov > Fix For: 4.3.0.Alpha1 > > > While trying to fix BZ1178874 I discovered that classes in src/test are not picked up as being valid beans to satisfy injection points. In the example in the Bugzilla issue (https://github.com/jboss-developer/jboss-eap-quickstarts/commit/7aa69072e...) it's a public static class being used, but even if that class is split off into its own public class it still isn't found as a valid bean. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19011) Switch Tern.java dependency version range to the only version before code freeze

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19011?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19011: -------------------------------- Summary: Switch Tern.java dependency version range to the only version before code freeze (was: Switch Tern.java dependency version rage to the only version before code freeze) > Switch Tern.java dependency version range to the only version before code freeze > -------------------------------------------------------------------------------- > > Key: JBIDE-19011 > URL: https://issues.jboss.org/browse/JBIDE-19011 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19023) CDI validation cannot find beans in src/test to be used for injection

by Jason Porter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19023?page=com.atlassian.jira.plugi... ] Jason Porter commented on JBIDE-19023: -------------------------------------- I had one in src/test/resources/META-INF/beans.xml. It may very well be similar to the aforementioned issue. > CDI validation cannot find beans in src/test to be used for injection > --------------------------------------------------------------------- > > Key: JBIDE-19023 > URL: https://issues.jboss.org/browse/JBIDE-19023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Jason Porter > Assignee: Alexey Kazakov > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > While trying to fix BZ1178874 I discovered that classes in src/test are not picked up as being valid beans to satisfy injection points. In the example in the Bugzilla issue (https://github.com/jboss-developer/jboss-eap-quickstarts/commit/7aa69072e...) it's a public static class being used, but even if that class is split off into its own public class it still isn't found as a valid bean. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18099) Configure Maven Repositories quickfix shows up on unrelated quickfixes

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18099?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18099: -------------------------------- Component/s: upstream > Configure Maven Repositories quickfix shows up on unrelated quickfixes > ---------------------------------------------------------------------- > > Key: JBIDE-18099 > URL: https://issues.jboss.org/browse/JBIDE-18099 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.3.x > > > I have a project where the groupid is the same as parent in many projects (i.e. javaee7-samples) > I get about 50 warnings about this and want to use the quickfix to remove this line. > I can't because our "Configure Maven Repositories" thinks it is a relevant fix for this issue. > Can we make it so it wont show up unless it is relevant ? > Screenshot: https://www.dropbox.com/s/dmo1a7x1em7qq06/Screenshot%202014-08-20%2012.51... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-306) Fuse: Add test case covers Camel Editor manipulation

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-306?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-306. ----------------------------------- already done, it works perfectly > Fuse: Add test case covers Camel Editor manipulation > ---------------------------------------------------- > > Key: JBTIS-306 > URL: https://issues.jboss.org/browse/JBTIS-306 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Original Estimate: 4 days > Time Spent: 4 days > Remaining Estimate: 0 minutes > > see relevant test cases in TCMS: https://tcms.engineering.redhat.com/plan/12241/jbds-fuse-tooling#testcases -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-344) Add test case covers 'JBoss Runtime Detection'

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-344?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-344. ----------------------------------- pr merged, it works fine > Add test case covers 'JBoss Runtime Detection' > ---------------------------------------------- > > Key: JBTIS-344 > URL: https://issues.jboss.org/browse/JBTIS-344 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Original Estimate: 4 days > Time Spent: 4 days > Remaining Estimate: 0 minutes > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-364) Fuse: Enhance XML parsing in tests

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-364?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-364. ----------------------------------- already done, it works perfectly > Fuse: Enhance XML parsing in tests > ---------------------------------- > > Key: JBTIS-364 > URL: https://issues.jboss.org/browse/JBTIS-364 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Original Estimate: 4 hours > Time Spent: 2 hours > Remaining Estimate: 2 hours > > use XPath validation in tests instead of comparison of file contents -- 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