November 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13352) Introduce @Category(FailingOnFirefox.class) to pom.xml

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13352 at 11/19/13 11:42 AM: ------------------------------------------------------------ Lukas, few implementation notes: <groups> and <exlucededGroups> is used to match what categories we want to run: http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#groups (note that <groups> should be rather named categories, but <groups> settings drives both, TestNG and JUnit tests, that's why maven-surefire-plugin follows TestNG naming conventions) The idea is that if you turn on profile, it can append boolean conditions as the suffix of <groups> selector. But I found that there is specific impl detail, which is not evident from first sight. During prototyping I have used <groups> together with <excludedGroups>, but platform-specific configuration (e.g. affects <groups>. That's why {{${testCategory.excluded.browser}}} needs to be setup as: {code} <testCategory.excluded.browser>AND NOT category.FailingOnFirefox</testCategory.excluded.browser> {code} You can use my prototype as a reference impl: https://github.com/lfryc/surefire-and-junit-categories/blob/master/pom.xm... was (Author: lfryc): Lukas, few implementation notes: <groups> and <exlucededGroups> is used to match what categories we want to run: http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#groups (note that <groups> should be rather named categories, but <groups> settings drives both, TestNG and JUnit tests, that's why maven-surefire-plugin follows TestNG naming conventions) The idea is that if you turn on profile, it can append boolean conditions as the suffix of <groups> selector. But I found that there is specific impl detail, which is not evident from first sight. During prototyping I have used <groups> together with <excludedGroups>, but platform-specific configuration (e.g. affects <groups>. That's why {{${testCategory.excluded.browser}}} needs to be setup as: {code} <testCategory.excluded.browser>AND NOT category.FailingFirefox</testCategory.excluded.browser> {code} You can use my prototype as a reference impl: https://github.com/lfryc/surefire-and-junit-categories/blob/master/pom.xm... > Introduce @Category(FailingOnFirefox.class) to pom.xml > ------------------------------------------------------ > > Key: RF-13352 > URL: https://issues.jboss.org/browse/RF-13352 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Lukáš Macko > Assignee: Lukáš Macko > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=c...], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests. > It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13357) Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13357?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13357: ---------------------------------- Assignee: Brian Leathem > Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version > -------------------------------------------------------------------------------------------- > > Key: RF-13357 > URL: https://issues.jboss.org/browse/RF-13357 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Lukáš Fryč > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13357) Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13357?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13357: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version > -------------------------------------------------------------------------------------------- > > Key: RF-13357 > URL: https://issues.jboss.org/browse/RF-13357 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Lukáš Fryč > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13359) Showcase: several components don't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13359: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 6 > Showcase: several components don't work > --------------------------------------- > > Key: RF-13359 > URL: https://issues.jboss.org/browse/RF-13359 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > Reporter: Pavol Pitonak > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progre... > # open browser console > # click on "Start Process" button > result: > * this message appears in browser console > {quote} > event.returnValue is deprecated. Please use the standard event.preventDefault() instead. > {quote} > * progress bar is rendered wrongly > * the same message is displayed on these pages (and these components are broken too) > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=toggle... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPan... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accord... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelM... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDr... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&... -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13359) Showcase: several components don't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13359: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Showcase: several components don't work > --------------------------------------- > > Key: RF-13359 > URL: https://issues.jboss.org/browse/RF-13359 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > Reporter: Pavol Pitonak > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progre... > # open browser console > # click on "Start Process" button > result: > * this message appears in browser console > {quote} > event.returnValue is deprecated. Please use the standard event.preventDefault() instead. > {quote} > * progress bar is rendered wrongly > * the same message is displayed on these pages (and these components are broken too) > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=toggle... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPan... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accord... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelM... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDr... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&... -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13359) Showcase: several components don't work

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.s... ] Michal Petrov commented on RF-13359: ------------------------------------ The warning messages are generated by the browser and the issue is in jQuery, I don't think it's soimething we directly use in RichFaces. See [http://bugs.jquery.com/ticket/14282]. > Showcase: several components don't work > --------------------------------------- > > Key: RF-13359 > URL: https://issues.jboss.org/browse/RF-13359 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > Reporter: Pavol Pitonak > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > > # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progre... > # open browser console > # click on "Start Process" button > result: > * this message appears in browser console > {quote} > event.returnValue is deprecated. Please use the standard event.preventDefault() instead. > {quote} > * progress bar is rendered wrongly > * the same message is displayed on these pages (and these components are broken too) > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=toggle... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPan... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accord... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelM... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDr... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&... -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13359) Showcase: several components don't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13359: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > Showcase: several components don't work > --------------------------------------- > > Key: RF-13359 > URL: https://issues.jboss.org/browse/RF-13359 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > Reporter: Pavol Pitonak > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > > # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progre... > # open browser console > # click on "Start Process" button > result: > * this message appears in browser console > {quote} > event.returnValue is deprecated. Please use the standard event.preventDefault() instead. > {quote} > * progress bar is rendered wrongly > * the same message is displayed on these pages (and these components are broken too) > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=toggle... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPan... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accord... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelM... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDr... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey... > ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&... -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13354) Autocomplete: suggestions stay visible after input is cleared

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13354?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-13354: ------------------------------- Assignee: Lukáš Fryč > Autocomplete: suggestions stay visible after input is cleared > ------------------------------------------------------------- > > Key: RF-13354 > URL: https://issues.jboss.org/browse/RF-13354 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "ala" into input (several suggestions will appear) > # clear input, e.g. by using backspace key > result: > * the list with all available suggestions is displayed > * in 4.3.4.Final, the suggestions are *not* displayed when input is empty -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13354) Autocomplete: suggestions stay visible after input is cleared

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13354?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13354: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Autocomplete: suggestions stay visible after input is cleared > ------------------------------------------------------------- > > Key: RF-13354 > URL: https://issues.jboss.org/browse/RF-13354 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "ala" into input (several suggestions will appear) > # clear input, e.g. by using backspace key > result: > * the list with all available suggestions is displayed > * in 4.3.4.Final, the suggestions are *not* displayed when input is empty -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-13352) Introduce @Category(FailingOnFirefox.class) to pom.xml

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13352: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 6 > Introduce @Category(FailingOnFirefox.class) to pom.xml > ------------------------------------------------------ > > Key: RF-13352 > URL: https://issues.jboss.org/browse/RF-13352 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Lukáš Macko > Assignee: Lukáš Macko > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=c...], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests. > It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2013