August 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13783) Placeholder: attribute styleClass doesn't work inside inplace input and inplace select

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13783?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13783: ------------------------------- Fix Version/s: 4.5.0.Beta2 > Placeholder: attribute styleClass doesn't work inside inplace input and inplace select > -------------------------------------------------------------------------------------- > > Key: RF-13783 > URL: https://issues.jboss.org/browse/RF-13783 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, component-misc > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavol Pitonak > Fix For: 4.5.0.Beta2 > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richPlaceholder/inplaceInp... > # set styleClass=xxx > expected: > * some element inside inplace input has class "xxx" so that placeholder can be customized > result: > * there is no element with given css class -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13782) Context menu, drop down menu: showEvent set to hover doesn't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13782?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13782: ------------------------------- Labels: regression (was: ) > Context menu, drop down menu: showEvent set to hover doesn't work > ----------------------------------------------------------------- > > Key: RF-13782 > URL: https://issues.jboss.org/browse/RF-13782 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, regression > Affects Versions: 4.5.0.Alpha3 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > Mojarra 2.1.28-jbossorg-2 > EAP 6.3.0 > Java(TM) SE Runtime Environment 1.7.0_51-b13 @ Linux > Firefox 31.0 @ Linux x86_64 > Reporter: Pavol Pitonak > Labels: regression > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richContextMenu/simple.xhtml > # set showEvent=hover > # move mouse cursor over green panel > OR > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richDropDownMenu/topMenu.x... > # set showEvent=hover > # move mouse cursor over menu item "File" > expected: > * context menu/drop down menu should be displayed > result: > * nothing happens > * it's a *regression*, works fine in 4.5.0.Alpha3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13782) Context menu, drop down menu: showEvent set to hover doesn't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13782?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13782: ------------------------------- Fix Version/s: 4.5.0.Beta1 > Context menu, drop down menu: showEvent set to hover doesn't work > ----------------------------------------------------------------- > > Key: RF-13782 > URL: https://issues.jboss.org/browse/RF-13782 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, regression > Affects Versions: 4.5.0.Alpha3 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > Mojarra 2.1.28-jbossorg-2 > EAP 6.3.0 > Java(TM) SE Runtime Environment 1.7.0_51-b13 @ Linux > Firefox 31.0 @ Linux x86_64 > Reporter: Pavol Pitonak > Labels: regression > Fix For: 4.5.0.Beta1 > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richContextMenu/simple.xhtml > # set showEvent=hover > # move mouse cursor over green panel > OR > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richDropDownMenu/topMenu.x... > # set showEvent=hover > # move mouse cursor over menu item "File" > expected: > * context menu/drop down menu should be displayed > result: > * nothing happens > * it's a *regression*, works fine in 4.5.0.Alpha3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13781) RF-4.5 compliment to JDK7 while WFK-2.7 must be compliment to JDK6

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13781?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13781: ------------------------------- Priority: Major (was: Critical) > RF-4.5 compliment to JDK7 while WFK-2.7 must be compliment to JDK6 > ------------------------------------------------------------------ > > Key: RF-13781 > URL: https://issues.jboss.org/browse/RF-13781 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavel Slegr > Fix For: 4.5.0.Beta1 > > > while building on RF-4.5 I found out there are used JDK7 features > for example here: https://github.com/richfaces/richfaces/blob/master/core/src/main/java/org... > (diamond operator) > RichFaces-4.5 are not able to build with JDK6, while as one of the components of WFK-27 > we would need to build them with JDK6 > WFK-2.7 will be based on EAP-6.3.0 which is based on JDK6 as well > There are 2 possible solutions > 1. We will go over the upstream code and remove all the JDK7 related code, which I have no idea, how much this would be. > 2. We will make it in productization branch only, which is not very wise due to future maintenance of WFK-27 and RF-45 following and > is exactly the opposite way we try to accomplish (get the product & upstream close as much as possible) > Please note, I am not able to crosscompile from 1.7 source into 1.6 target bytecode... this is not allowed > (http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javac.html) > cloned from https://issues.jboss.org/browse/WFK2-735 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13781) RF-4.5 compliment to JDK7 while WFK-2.7 must be compliment to JDK6

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13781?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13781: ------------------------------- Fix Version/s: 4.5.0.Beta2 (was: 4.5.0.Beta1) > RF-4.5 compliment to JDK7 while WFK-2.7 must be compliment to JDK6 > ------------------------------------------------------------------ > > Key: RF-13781 > URL: https://issues.jboss.org/browse/RF-13781 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavel Slegr > Fix For: 4.5.0.Beta2 > > > while building on RF-4.5 I found out there are used JDK7 features > for example here: https://github.com/richfaces/richfaces/blob/master/core/src/main/java/org... > (diamond operator) > RichFaces-4.5 are not able to build with JDK6, while as one of the components of WFK-27 > we would need to build them with JDK6 > WFK-2.7 will be based on EAP-6.3.0 which is based on JDK6 as well > There are 2 possible solutions > 1. We will go over the upstream code and remove all the JDK7 related code, which I have no idea, how much this would be. > 2. We will make it in productization branch only, which is not very wise due to future maintenance of WFK-27 and RF-45 following and > is exactly the opposite way we try to accomplish (get the product & upstream close as much as possible) > Please note, I am not able to crosscompile from 1.7 source into 1.6 target bytecode... this is not allowed > (http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javac.html) > cloned from https://issues.jboss.org/browse/WFK2-735 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13778) RF-45 cyclic dependency on richfaces-parent

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13778?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13778: ------------------------------------ [~pslegr] as I explained previously: the original plan was to deprecate jsf-test in favor of Arquillian-based Graphene tests. This plan has been put aside when we decided not to pursue RichFaces 5. As such we are stuck with using and maintaining the legacy jsf-test project. To resolve this conflict I propose we have jsf-test use jboss-parent and independently set any versions required from the RichFaces project. We will have to maintain duplicate versions in some places, but this is manageable. More manageable IMO than again separating richfaces-parent out into a separate repo. > RF-45 cyclic dependency on richfaces-parent > ------------------------------------------- > > Key: RF-13778 > URL: https://issues.jboss.org/browse/RF-13778 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavol Pitonak > Priority: Blocker > Fix For: 4.5.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Historically there is a dependency in .../jsf-tests/pom.xml on richfaces-parent which used to be a standalone project/repo in 4.3.x > {code} > <parent> > <groupId>org.richfaces</groupId> > <artifactId>richfaces-parent</artifactId> > <version>12</version> > </parent> > {code} > However nowadays in 4.5.x there is playing the role of parent the > richfaces/pom.xml > https://github.com/richfaces/richfaces/blob/master/pom.xml > {code} > <groupId>org.richfaces</groupId> > <artifactId>richfaces-parent</artifactId> > <packaging>pom</packaging> > <version>4.5.0-SNAPSHOT</version> > <name>RichFaces Parent</name> > {code} > which makes a cyclic dependency > jsf-test --> richfaces --> jsf-test > as there are inside https://github.com/richfaces/richfaces/blob/master/build/pom.xml > referenced dependencies for jsf-tests > {code} > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>htmlunit-client</artifactId> > <version>${version.jsf-test}</version> > <exclusions> > <exclusion> > <groupId>javax.servlet</groupId> > <artifactId>javax.servlet-api</artifactId> > </exclusion> > </exclusions> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-test-stage</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-mock</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-mockito</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-test-scriptunit</artifactId> > <version>${version.jsf-test}</version> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13778) RF-45 cyclic dependency on richfaces-parent

by Pavel Slegr (JIRA)

[ https://issues.jboss.org/browse/RF-13778?page=com.atlassian.jira.plugin.s... ] Pavel Slegr commented on RF-13778: ---------------------------------- > org.richfaces;richfaces-parent:12 shall be used with jsf-test. > org.richfaces:richfaces-parent:4.5.x shall be used with the framework. Well you do suggest here to use the 2 different version's of the same artifact (richface-parent) for 2 different projects IMO this mixing of GAV's is not nice and is not clear solution. When you planned to unify richfaces-4.3.x separated repositories into one single repository in 4.5.x then another name should be used Once org.richfaces;richfaces-parent:12 would be used with jsf-test. it means parent repository should be moved over to 4.5.x as well.... It is somehow messed up > RF-45 cyclic dependency on richfaces-parent > ------------------------------------------- > > Key: RF-13778 > URL: https://issues.jboss.org/browse/RF-13778 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavol Pitonak > Priority: Blocker > Fix For: 4.5.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Historically there is a dependency in .../jsf-tests/pom.xml on richfaces-parent which used to be a standalone project/repo in 4.3.x > {code} > <parent> > <groupId>org.richfaces</groupId> > <artifactId>richfaces-parent</artifactId> > <version>12</version> > </parent> > {code} > However nowadays in 4.5.x there is playing the role of parent the > richfaces/pom.xml > https://github.com/richfaces/richfaces/blob/master/pom.xml > {code} > <groupId>org.richfaces</groupId> > <artifactId>richfaces-parent</artifactId> > <packaging>pom</packaging> > <version>4.5.0-SNAPSHOT</version> > <name>RichFaces Parent</name> > {code} > which makes a cyclic dependency > jsf-test --> richfaces --> jsf-test > as there are inside https://github.com/richfaces/richfaces/blob/master/build/pom.xml > referenced dependencies for jsf-tests > {code} > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>htmlunit-client</artifactId> > <version>${version.jsf-test}</version> > <exclusions> > <exclusion> > <groupId>javax.servlet</groupId> > <artifactId>javax.servlet-api</artifactId> > </exclusion> > </exclusions> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-test-stage</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-mock</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-mockito</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-test-scriptunit</artifactId> > <version>${version.jsf-test}</version> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13778) RF-45 cyclic dependency on richfaces-parent

by Pavel Slegr (JIRA)

[ https://issues.jboss.org/browse/RF-13778?page=com.atlassian.jira.plugin.s... ] Pavel Slegr commented on RF-13778: ---------------------------------- in current RF-4.5.0.Alpha3 release there are defined dependencies to jsf-tests So, you can not claim it is deprecated When it is deprecated, then it should be removed, that is how I understand that. In case it will be removed, no code requires those. But my impression was the jsf-tests are still present for some reason, am I wrong [~bleathem] ? > RF-45 cyclic dependency on richfaces-parent > ------------------------------------------- > > Key: RF-13778 > URL: https://issues.jboss.org/browse/RF-13778 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavol Pitonak > Priority: Blocker > Fix For: 4.5.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Historically there is a dependency in .../jsf-tests/pom.xml on richfaces-parent which used to be a standalone project/repo in 4.3.x > {code} > <parent> > <groupId>org.richfaces</groupId> > <artifactId>richfaces-parent</artifactId> > <version>12</version> > </parent> > {code} > However nowadays in 4.5.x there is playing the role of parent the > richfaces/pom.xml > https://github.com/richfaces/richfaces/blob/master/pom.xml > {code} > <groupId>org.richfaces</groupId> > <artifactId>richfaces-parent</artifactId> > <packaging>pom</packaging> > <version>4.5.0-SNAPSHOT</version> > <name>RichFaces Parent</name> > {code} > which makes a cyclic dependency > jsf-test --> richfaces --> jsf-test > as there are inside https://github.com/richfaces/richfaces/blob/master/build/pom.xml > referenced dependencies for jsf-tests > {code} > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>htmlunit-client</artifactId> > <version>${version.jsf-test}</version> > <exclusions> > <exclusion> > <groupId>javax.servlet</groupId> > <artifactId>javax.servlet-api</artifactId> > </exclusion> > </exclusions> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-test-stage</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-mock</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-mockito</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-test-scriptunit</artifactId> > <version>${version.jsf-test}</version> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13778) RF-45 cyclic dependency on richfaces-parent

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13778?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13778: --------------------------------- {{richfaces-parent <= 12}} is deprecated and so is {{jsf-test}}. > RF-45 cyclic dependency on richfaces-parent > ------------------------------------------- > > Key: RF-13778 > URL: https://issues.jboss.org/browse/RF-13778 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavol Pitonak > Priority: Blocker > Fix For: 4.5.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Historically there is a dependency in .../jsf-tests/pom.xml on richfaces-parent which used to be a standalone project/repo in 4.3.x > {code} > <parent> > <groupId>org.richfaces</groupId> > <artifactId>richfaces-parent</artifactId> > <version>12</version> > </parent> > {code} > However nowadays in 4.5.x there is playing the role of parent the > richfaces/pom.xml > https://github.com/richfaces/richfaces/blob/master/pom.xml > {code} > <groupId>org.richfaces</groupId> > <artifactId>richfaces-parent</artifactId> > <packaging>pom</packaging> > <version>4.5.0-SNAPSHOT</version> > <name>RichFaces Parent</name> > {code} > which makes a cyclic dependency > jsf-test --> richfaces --> jsf-test > as there are inside https://github.com/richfaces/richfaces/blob/master/build/pom.xml > referenced dependencies for jsf-tests > {code} > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>htmlunit-client</artifactId> > <version>${version.jsf-test}</version> > <exclusions> > <exclusion> > <groupId>javax.servlet</groupId> > <artifactId>javax.servlet-api</artifactId> > </exclusion> > </exclusions> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-test-stage</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-mock</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-mockito</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-test-scriptunit</artifactId> > <version>${version.jsf-test}</version> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13778) RF-45 cyclic dependency on richfaces-parent

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13778?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13778: --------------------------------- {{org.richfaces;richfaces-parent:12}} shall be used with {{jsf-test}}. {{org.richfaces:richfaces-parent:4.5.x}} shall be used with the framework. > RF-45 cyclic dependency on richfaces-parent > ------------------------------------------- > > Key: RF-13778 > URL: https://issues.jboss.org/browse/RF-13778 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavol Pitonak > Priority: Blocker > Fix For: 4.5.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Historically there is a dependency in .../jsf-tests/pom.xml on richfaces-parent which used to be a standalone project/repo in 4.3.x > {code} > <parent> > <groupId>org.richfaces</groupId> > <artifactId>richfaces-parent</artifactId> > <version>12</version> > </parent> > {code} > However nowadays in 4.5.x there is playing the role of parent the > richfaces/pom.xml > https://github.com/richfaces/richfaces/blob/master/pom.xml > {code} > <groupId>org.richfaces</groupId> > <artifactId>richfaces-parent</artifactId> > <packaging>pom</packaging> > <version>4.5.0-SNAPSHOT</version> > <name>RichFaces Parent</name> > {code} > which makes a cyclic dependency > jsf-test --> richfaces --> jsf-test > as there are inside https://github.com/richfaces/richfaces/blob/master/build/pom.xml > referenced dependencies for jsf-tests > {code} > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>htmlunit-client</artifactId> > <version>${version.jsf-test}</version> > <exclusions> > <exclusion> > <groupId>javax.servlet</groupId> > <artifactId>javax.servlet-api</artifactId> > </exclusion> > </exclusions> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-test-stage</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-mock</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-mockito</artifactId> > <version>${version.jsf-test}</version> > </dependency> > <dependency> > <groupId>org.jboss.test-jsf</groupId> > <artifactId>jsf-test-scriptunit</artifactId> > <version>${version.jsf-test}</version> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 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 August 2014