[JBoss JIRA] (RF-13001) Archetypes are not released
by Jan Papousek (JIRA)
Jan Papousek created RF-13001:
---------------------------------
Summary: Archetypes are not released
Key: RF-13001
URL: https://issues.jboss.org/browse/RF-13001
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: archetype
Affects Versions: 5.0.0.Alpha1
Reporter: Jan Papousek
Priority: Blocker
Archetypes are not available in staging repository.
--
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, 10 months
[JBoss JIRA] (RF-13000) RichFaces 5 cannot be built on Windows
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13000?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13000:
----------------------------------
Assignee: Lukáš Fryč
[~lfryc] Please have a look at this, and determine if the fix is in the scope of 5.0.0.Alpha1 (keeping in mind we have a large number of Widows users)
> RichFaces 5 cannot be built on Windows
> --------------------------------------
>
> Key: RF-13000
> URL: https://issues.jboss.org/browse/RF-13000
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Environment: Windows 8 x64
> Maven 3.0.4
> Oracle JDK 1.7.0_07
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 5.0.0.Alpha1
>
>
> # git clone git://github.com/richfaces/richfaces.git
> # cd richfaces
> # mvn clean install
> result:
> * and error in "framework" module caused by UTF-8 characters (left/right arrow)
> {quote}
> [ERROR] unmappable character for encoding windows-1252, in the file:W:\workspace\richfaces-5.0-chrome\richfaces\framework\src\main\java\org\richfaces\ui\select\pickList\AbstractPickList.java at line 80 in column 34
> [ERROR] unmappable character for encoding windows-1252, in the file:W:\workspace\richfaces-5.0-chrome\richfaces\framework\src\main\java\org\richfaces\ui\select\pickList\AbstractPickList.java at line 86 in column 34
> {quote}
--
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, 10 months
[JBoss JIRA] (RF-12974) Create a richfaces-push depchain
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12974?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12974.
--------------------------------
Resolution: Done
> Create a richfaces-push depchain
> --------------------------------
>
> Key: RF-12974
> URL: https://issues.jboss.org/browse/RF-12974
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha1
>
> Original Estimate: 1 hour, 30 minutes
> Remaining Estimate: 1 hour, 30 minutes
>
> Create a _richfaces-push_ depchain to transitively bring in the atmosphere dependencies of the correct version.
> While at it, move the dependency management of the richfaces and richfaces-push depchains out of the user-facing BOM and into the build BOM.
--
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, 10 months
[JBoss JIRA] (RF-12974) Create a richfaces-push depchain
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12974?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12974:
------------------------------------
The richfaces-push depchain should be used in any example that previously included the atmosphere dependency.
The version of the artifacts in the richfaces-push depchain *are* managed by the build bom via the richfaces-parent.
> Create a richfaces-push depchain
> --------------------------------
>
> Key: RF-12974
> URL: https://issues.jboss.org/browse/RF-12974
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha1
>
> Original Estimate: 1 hour, 30 minutes
> Remaining Estimate: 1 hour, 30 minutes
>
> Create a _richfaces-push_ depchain to transitively bring in the atmosphere dependencies of the correct version.
> While at it, move the dependency management of the richfaces and richfaces-push depchains out of the user-facing BOM and into the build BOM.
--
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, 10 months
[JBoss JIRA] (RF-12999) Showcase - deployment on Tomcat 6 with errors
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12999?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12999.
--------------------------------
Assignee: Brian Leathem
Fix Version/s: (was: 5.0.0.Alpha1)
Resolution: Out of Date
Resolved with RF-12998
> Showcase - deployment on Tomcat 6 with errors
> ---------------------------------------------
>
> Key: RF-12999
> URL: https://issues.jboss.org/browse/RF-12999
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: regression, showcase
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
>
> Showcase can not be deployed on Tomcat 6.
> This is the log from the server:
> {code}
> SEVERE: Unable to instantiate ExpressionFactory 'com.sun.el.ExpressionFactoryImpl'
> May 21, 2013 11:17:13 AM com.sun.faces.config.ConfigureListener contextInitialized
> SEVERE: Critical error during deployment:
> com.sun.faces.config.ConfigurationException: It appears the JSP version of the container is older than 2.1 and unable to locate t
> he EL RI expression factory, com.sun.el.ExpressionFactoryImpl. If not using JSP or the EL RI, make sure the context initializati
> on parameter, com.sun.faces.expressionFactory, is properly set.
> at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:645)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:234)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
> at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:563)
> at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1399)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791)
> at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1500)
> at org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:670)
> at org.apache.catalina.manager.ManagerServlet.doPut(ManagerServlet.java:435)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:640)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:722)
> May 21, 2013 11:17:13 AM org.apache.catalina.core.StandardContext listenerStart
> SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
> java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: It appears the JSP version of the container is older tha
> n 2.1 and unable to locate the EL RI expression factory, com.sun.el.ExpressionFactoryImpl. If not using JSP or the EL RI, make s
> ure the context initialization parameter, com.sun.faces.expressionFactory, is properly set.
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:276)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
> at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:563)
> at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1399)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791)
> at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1500)
> at org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:670)
> at org.apache.catalina.manager.ManagerServlet.doPut(ManagerServlet.java:435)
> Caused by: com.sun.faces.config.ConfigurationException: It appears the JSP version of the container is older than 2.1 and unable to locate the EL RI expression factory, com.sun.el.ExpressionFactoryImpl. If not using JSP or the EL RI, make sure the context initialization parameter, com.sun.faces.expressionFactory, is properly set.
> at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:645)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:234)
> ... 33 more
> {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, 10 months
[JBoss JIRA] (RF-12998) Showcase - resource handling errors for all demos on Tomcat 7
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12998?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12998.
--------------------------------
Assignee: Brian Leathem
Resolution: Done
There were two issues embeded here.
1) the error in the server output which I corrected by marking the servlet APIs as <provided>
2) The resource loading error, which I fixed by correcting the ResourceServlet package in the web.xml
I also tidied up the schema declaration of the tomcat web.xml file.
@QE Please verify the showcase again in all containers, as the pom.xml change affects more than just the tomcat deployment.
> Showcase - resource handling errors for all demos on Tomcat 7
> -------------------------------------------------------------
>
> Key: RF-12998
> URL: https://issues.jboss.org/browse/RF-12998
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: regression, resource handling, showcase
> Affects Versions: 5.0.0.Alpha1
> Environment: Tomcat 7
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Blocker
> Fix For: 5.0.0.Alpha1
>
> Attachments: resourceWrong.png
>
>
> This is noticeable after resolving RF-12996 locally.
> There are lot of resource not found and JQUery not defined JS errors when loading showcase on Tomcat 7. It is so for all demos.
--
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, 10 months
[JBoss JIRA] (RF-12998) Showcase - resource handling errors for all demos on Tomcat 7
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12998?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12998:
------------------------------------
Note the error message in the server log:
{quote}
INFO: validateJarFile(/opt/apache/tomcat7/webapps/richfaces-showcase-tomcat6/WEB-INF/lib/jboss-servlet-api_3.0_spec-1.0.1.Final.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
{quote}
The webapp is trying to validate a servlet 3.0 jar according to the 2.3 spec. I believe this was introduced with this commit:
https://github.com/richfaces/richfaces/commit/97889cfc58d8e7662d462151afc...
> Showcase - resource handling errors for all demos on Tomcat 7
> -------------------------------------------------------------
>
> Key: RF-12998
> URL: https://issues.jboss.org/browse/RF-12998
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: regression, resource handling, showcase
> Affects Versions: 5.0.0.Alpha1
> Environment: Tomcat 7
> Reporter: Juraj Húska
> Priority: Blocker
> Fix For: 5.0.0.Alpha1
>
> Attachments: resourceWrong.png
>
>
> This is noticeable after resolving RF-12996 locally.
> There are lot of resource not found and JQUery not defined JS errors when loading showcase on Tomcat 7. It is so for all demos.
--
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, 10 months