March 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12749) Enforce Unix line endings pre-commit or during build

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12749?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12749: ------------------------------- Issue Type: Component Upgrade (was: Sub-task) > Enforce Unix line endings pre-commit or during build > ---------------------------------------------------- > > Key: RF-12749 > URL: https://issues.jboss.org/browse/RF-12749 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.M1 > Reporter: Lukáš Fryč > Fix For: 5.0.0.M1 > > > https://help.github.com/articles/dealing-with-line-endings > http://stackoverflow.com/questions/2332349/best-practices-for-cross-platf... -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12467) Decouple CDK from RichFaces build

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12467?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12467: ------------------------------- Issue Type: Component Upgrade (was: Sub-task) > Decouple CDK from RichFaces build > --------------------------------- > > Key: RF-12467 > URL: https://issues.jboss.org/browse/RF-12467 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.M1 > > > According to diagram at: > https://community.jboss.org/wiki/RichFaces43BuildRedesign > It should not depend on RichFaces framework anymore. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12451) Merge core/components/build/dev-examples repositories

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12451?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12451: ------------------------------- Issue Type: Component Upgrade (was: Sub-task) > Merge core/components/build/dev-examples repositories > ----------------------------------------------------- > > Key: RF-12451 > URL: https://issues.jboss.org/browse/RF-12451 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.M1 > > > It's necessary to preserve history of commits -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12742) Merge CR2 and further commits from richfaces4 repos to richfaces5 repo

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12742?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12742: ------------------------------- Issue Type: Component Upgrade (was: Sub-task) > Merge CR2 and further commits from richfaces4 repos to richfaces5 repo > ---------------------------------------------------------------------- > > Key: RF-12742 > URL: https://issues.jboss.org/browse/RF-12742 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 5.0.0.M1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12806) Remote configuration in the arquillian.xml file should be commented - See JDF-215 for details

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12806?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12806: ------------------------------- Fix Version/s: 4.3.2 (was: 4.2.4) > Remote configuration in the arquillian.xml file should be commented - See JDF-215 for details > --------------------------------------------------------------------------------------------- > > Key: RF-12806 > URL: https://issues.jboss.org/browse/RF-12806 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > Fix For: 4.3.2, 5.0.0.M2 > > > The kitchensink-rf arquillian.xml file contains a configuration for jbossHome > This should be commented out. All the remote configuration in the arquillian files should look like the following: >  > <container qualifier="jboss" default="true"> >  >  >  >  > </container> > You can copy and paste from the bean-validation arquillian.xml file. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12809) Richfaces-related examples should use -with-richfaces BOM

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12809: ------------------------------- Fix Version/s: 4.3.2 (was: 4.2.4) > Richfaces-related examples should use -with-richfaces BOM > --------------------------------------------------------- > > Key: RF-12809 > URL: https://issues.jboss.org/browse/RF-12809 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Tomas Repel > Fix For: 4.3.2, 5.0.0.M2 > > > There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation. In case of helloworld-rf it is sufficient the dependencyManagement section to contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed completely. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12834) forge plugin - update version of richfaces to 4.2.3.Final and 4.3.1.Final

by Jan Papousek (JIRA)

Jan Papousek created RF-12834: --------------------------------- Summary: forge plugin - update version of richfaces to 4.2.3.Final and 4.3.1.Final Key: RF-12834 URL: https://issues.jboss.org/browse/RF-12834 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jan Papousek -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12809) Richfaces-related examples should use -with-richfaces BOM

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-12809: ---------------------------------------------- Tomas Repel <trepel(a)redhat.com> changed the Status of [bug 915767|https://bugzilla.redhat.com/show_bug.cgi?id=915767] from ON_QA to VERIFIED > Richfaces-related examples should use -with-richfaces BOM > --------------------------------------------------------- > > Key: RF-12809 > URL: https://issues.jboss.org/browse/RF-12809 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Tomas Repel > Fix For: 4.2.4, 5.0.0.M2 > > > There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation. In case of helloworld-rf it is sufficient the dependencyManagement section to contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed completely. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12809) Richfaces-related examples should use -with-richfaces BOM

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-12809: ---------------------------------------------- Tomas Repel <trepel(a)redhat.com> made a comment on [bug 915767|https://bugzilla.redhat.com/show_bug.cgi?id=915767] Verified in WFK 2.2.0.ER2. > Richfaces-related examples should use -with-richfaces BOM > --------------------------------------------------------- > > Key: RF-12809 > URL: https://issues.jboss.org/browse/RF-12809 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Tomas Repel > Fix For: 4.2.4, 5.0.0.M2 > > > There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation. In case of helloworld-rf it is sufficient the dependencyManagement section to contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed completely. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12832) Tomcat 6 test Deployments should define the expressionFactory

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12832?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12832 at 3/10/13 4:09 PM: ---------------------------------------------------------- We can simply fix this in M1. was (Author: lfryc): We can simply fix this in M!. > Tomcat 6 test Deployments should define the expressionFactory > ------------------------------------------------------------- > > Key: RF-12832 > URL: https://issues.jboss.org/browse/RF-12832 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 5.0.0.M1 > > > JBoss EL is added as a dependency for tomcat deployments, however the expressionFactory needs to be configured to use the bundled EL implementation. > Without the configuration below, tests that use advanced EL features will fail on Tomcat. > For Mojarra implementations, the web.xml of the Deployment should contain: > {code} > <context-param> > <param-name>com.sun.faces.expressionFactory</param-name> > <param-value>org.jboss.el.ExpressionFactoryImpl</param-value> > </context-param> > {code} > And MyFaces implementations, the web.xml of the Deployment should contain: > {code} > <context-param> > <param-name>org.apache.myfaces.EXPRESSION_FACTORY</param-name> > <param-value>org.jboss.el.ExpressionFactoryImpl</param-value> > </context-param> > {code} -- 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

12 years, 12 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

richfaces-issues March 2013