[JBoss JIRA] (RF-13759) Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13759?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13759:
----------------------------------
Assignee: Brian Leathem
> Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0
> -----------------------------------------------------------------------------
>
> Key: RF-13759
> URL: https://issues.jboss.org/browse/RF-13759
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk, component, core
> Affects Versions: 4.5.0.Alpha3
> Reporter: Pavel Slegr
> Assignee: Brian Leathem
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> both cdk and richfaces projects use different jboss-parent versions (9,12)
> EAP-6.3.0 which will be underlying base for RF\-4.5.0 uses as latest supported jboss-parent version 11.
> Please unify into jboss-parent 11
> NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo
> These classes use deprecated api such as
> {code}
> @parameter expression="${executedProject}""
> {code}
> which doesn't work with maven-plugin-plugin 3.1 and leads into
> {code}
> [WARNING] The syntax
> [WARNING] @parameter expression="${property}"
> [WARNING] is deprecated, please use
> [WARNING] @parameter property="property"
> [WARNING] instead.
> {code}
> Some other additional changes may be also needed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13753) Upgrade Atmosphere to 2.2.0
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13753?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13753:
----------------------------------
Assignee: Brian Leathem
> Upgrade Atmosphere to 2.2.0
> ---------------------------
>
> Key: RF-13753
> URL: https://issues.jboss.org/browse/RF-13753
> Project: RichFaces
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.7, 5.0.0.Alpha3
> Reporter: Thomas Amrhein
> Assignee: Brian Leathem
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Upgrade Atmosphere from 1.0.18 to 2.2.0.
> Reason: Many bugfixes, improved compatibility to many servers, ...
> For us: Also upgrade in 4.3.x is required.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13753) Upgrade Atmosphere to 2.2.0
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13753?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13753:
------------------------------------
I updated atmosphere, see the branch {{[RF-13753-upgrade-atmosphere|https://github.com/richfaces/richfaces/tree/RF-13753-upgrade-atmosphere]}}.
However a logging configuration problem in Undertow (WFLY-3722) causes an exception to be thrown everytime one navigates away from a page containing the push component.
It does however work without error on JBoss EAP 6.3.0.Beta.
> Upgrade Atmosphere to 2.2.0
> ---------------------------
>
> Key: RF-13753
> URL: https://issues.jboss.org/browse/RF-13753
> Project: RichFaces
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.7, 5.0.0.Alpha3
> Reporter: Thomas Amrhein
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Upgrade Atmosphere from 1.0.18 to 2.2.0.
> Reason: Many bugfixes, improved compatibility to many servers, ...
> For us: Also upgrade in 4.3.x is required.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13759) Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13759?page=com.atlassian.jira.plugin.s... ]
Marek Novotny commented on RF-13759:
------------------------------------
[~bleathem] RichFaces-cdk is not a runtime library that is true, but we are here speaking about better maintability which is the main target for doing 4.5.x instead of 4.3.x, right?
With regarding to jboss-parent we are pretty sure as EAP 6.3.0.GA was released this week with version 11 of jboss-parent and EAP team will do only bug fixing in patch releases. We are bound now with 6.3.x for WFK 2.7.0. Exceptions happen but that is now really very low probability. Please evaluate it and let us know what features are required from org.jboss:jboss-parent:12 ? Otherwise we will differ between project/product release - less maintainability after deprecation.
> Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0
> -----------------------------------------------------------------------------
>
> Key: RF-13759
> URL: https://issues.jboss.org/browse/RF-13759
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk, component, core
> Affects Versions: 4.5.0.Alpha3
> Reporter: Pavel Slegr
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> both cdk and richfaces projects use different jboss-parent versions (9,12)
> EAP-6.3.0 which will be underlying base for RF\-4.5.0 uses as latest supported jboss-parent version 11.
> Please unify into jboss-parent 11
> NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo
> These classes use deprecated api such as
> {code}
> @parameter expression="${executedProject}""
> {code}
> which doesn't work with maven-plugin-plugin 3.1 and leads into
> {code}
> [WARNING] The syntax
> [WARNING] @parameter expression="${property}"
> [WARNING] is deprecated, please use
> [WARNING] @parameter property="property"
> [WARNING] instead.
> {code}
> Some other additional changes may be also needed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13768) Tests for inplaceInput and inplaceSelect renderer failing
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13768?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13768:
------------------------------------
I'm concerned that the fix for RF-13758 means the resource requests aren't being routed through our resource servlet. I'm waiting to resolve this issue until I'm satisfied the patch that broke this test is correct.
> Tests for inplaceInput and inplaceSelect renderer failing
> ---------------------------------------------------------
>
> Key: RF-13768
> URL: https://issues.jboss.org/browse/RF-13768
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, resource handling
> Affects Versions: 4.5.0.Alpha3
> Reporter: Pavol Pitonak
> Assignee: Brian Leathem
> Priority: Blocker
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> Two tests for inplace input and inplace select started failing. Investigate if the change in rendered HTML is expected.
> {code}
> InplaceInputRendererTest.testDefaultWithControlsEncode:29->InplaceRendererTestBase.doTestDefaultWithControlsEncode:29->RendererTestBase.doTest:91->RendererTestBase.checkXmlStructure:114 XML was not similar:org.custommonkey.xmlunit.Diff
> [different] Expected attribute value '/org.richfaces.resources/javax.faces.resource/org.richfaces/ico_ok.gif' but was '/javax.faces.resource/ico_ok.gif.jsf?ln=org.richfaces' - comparing <input src="/org.richfaces.resources/javax.faces.resource/org.richfaces/ico_ok.gif"...> at /span[1]/span[2]/span[1]/span[1]/span[1]/span[5]/input[1]/@src to <input src="/javax.faces.resource/ico_ok.gif.jsf?ln=org.richfaces"...> at /span[1]/span[2]/span[1]/span[1]/span[1]/span[5]/input[1]/@src
> {code}
> {code}
> InplaceSelectRendererTest.testDefaultWithControlsEncode:32->InplaceRendererTestBase.doTestDefaultWithControlsEncode:29->RendererTestBase.doTest:91->RendererTestBase.checkXmlStructure:114 XML was not similar:org.custommonkey.xmlunit.Diff
> [different] Expected attribute value '/org.richfaces.resources/javax.faces.resource/org.richfaces/ico_ok.gif' but was '/javax.faces.resource/ico_ok.gif.jsf?ln=org.richfaces' - comparing <input src="/org.richfaces.resources/javax.faces.resource/org.richfaces/ico_ok.gif"...> at /span[1]/span[2]/span[1]/span[1]/span[1]/span[5]/input[1]/@src to <input src="/javax.faces.resource/ico_ok.gif.jsf?ln=org.richfaces"...> at /span[1]/span[2]/span[1]/span[1]/span[1]/span[5]/input[1]/@src
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13759) Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13759?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13759:
------------------------------------
RichFaces-cdk is not a runtime library. It is merely used to build the RichFaces project. As such a release for the sole purpose of updating the parent seems superfluous.
Also, is downgrading RichFaces 4.5 to use 11 instead of 12 necessary? Are we sure we won't see a EAP micro release with an updated parent before WFK 2.7 ships?
> Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0
> -----------------------------------------------------------------------------
>
> Key: RF-13759
> URL: https://issues.jboss.org/browse/RF-13759
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk, component, core
> Affects Versions: 4.5.0.Alpha3
> Reporter: Pavel Slegr
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> both cdk and richfaces projects use different jboss-parent versions (9,12)
> EAP-6.3.0 which will be underlying base for RF\-4.5.0 uses as latest supported jboss-parent version 11.
> Please unify into jboss-parent 11
> NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo
> These classes use deprecated api such as
> {code}
> @parameter expression="${executedProject}""
> {code}
> which doesn't work with maven-plugin-plugin 3.1 and leads into
> {code}
> [WARNING] The syntax
> [WARNING] @parameter expression="${property}"
> [WARNING] is deprecated, please use
> [WARNING] @parameter property="property"
> [WARNING] instead.
> {code}
> Some other additional changes may be also needed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13759) Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13759?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13759:
-------------------------------
Description:
both cdk and richfaces projects use different jboss-parent versions (9,12)
EAP-6.3.0 which will be underlying base for RF\-4.5.0 uses as latest supported jboss-parent version 11.
Please unify into jboss-parent 11
NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo
These classes use deprecated api such as
{code}
@parameter expression="${executedProject}""
{code}
which doesn't work with maven-plugin-plugin 3.1 and leads into
{code}
[WARNING] The syntax
[WARNING] @parameter expression="${property}"
[WARNING] is deprecated, please use
[WARNING] @parameter property="property"
[WARNING] instead.
{code}
Some other additional changes may be also needed.
was:
both cdk and richfaces projects use different jboss-parent versions (9,12)
EAP-6.3.0 which will be underlying base for RF-4.5.0 uses as latest supported jboss-parent version 11.
Please unify into jboss-parent 11
NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo
These classes use deprecated api such as
{code}
@parameter expression="${executedProject}""
{code}
which doesn't work with maven-plugin-plugin 3.1 and leads into
{code}
[WARNING] The syntax
[WARNING] @parameter expression="${property}"
[WARNING] is deprecated, please use
[WARNING] @parameter property="property"
[WARNING] instead.
{code}
Some other additional changes may be also needed.
> Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0
> -----------------------------------------------------------------------------
>
> Key: RF-13759
> URL: https://issues.jboss.org/browse/RF-13759
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk, component, core
> Affects Versions: 4.5.0.Alpha3
> Reporter: Pavel Slegr
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> both cdk and richfaces projects use different jboss-parent versions (9,12)
> EAP-6.3.0 which will be underlying base for RF\-4.5.0 uses as latest supported jboss-parent version 11.
> Please unify into jboss-parent 11
> NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo
> These classes use deprecated api such as
> {code}
> @parameter expression="${executedProject}""
> {code}
> which doesn't work with maven-plugin-plugin 3.1 and leads into
> {code}
> [WARNING] The syntax
> [WARNING] @parameter expression="${property}"
> [WARNING] is deprecated, please use
> [WARNING] @parameter property="property"
> [WARNING] instead.
> {code}
> Some other additional changes may be also needed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13758) RF 4.5 with MyFaces, CSS not loaded
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13758?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13758:
------------------------------------
[~lfryc] can you comment on the validity of this fix? What is the consequence of removing _org.richfaces_ from the _RESOURCE_LIBRARIES_TO_MAP_ list?
> RF 4.5 with MyFaces, CSS not loaded
> -----------------------------------
>
> Key: RF-13758
> URL: https://issues.jboss.org/browse/RF-13758
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.5.0.Alpha3
> Reporter: Matej Novotny
> Assignee: Michal Petrov
> Priority: Critical
> Labels: myfaces, needs-qe
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> When you use MyFaces as JSF implementation, RF fail to get CSS files hence the components are displayed as plain text.
> I tried this (among others) with simpleapp which I modified by adding a simple rich:panel. With Mojarra the css for panel was received and panel was displayed correctly. Then I modified pom.xml to use MyFaces. The app can be deployed but the panel is just a plain text and page contains no css for styling.
> This can be reproduced with Metamer/simpleapp/showcase.
> Please see steps to reproduce for reproducers with Metamer and simpleapp.
> Showcase reproducer is more complicated due to RF-13757.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13768) Tests for inplaceInput and inplaceSelect renderer failing
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13768?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13768:
----------------------------------
Assignee: Brian Leathem
> Tests for inplaceInput and inplaceSelect renderer failing
> ---------------------------------------------------------
>
> Key: RF-13768
> URL: https://issues.jboss.org/browse/RF-13768
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, resource handling
> Affects Versions: 4.5.0.Alpha3
> Reporter: Pavol Pitonak
> Assignee: Brian Leathem
> Priority: Blocker
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> Two tests for inplace input and inplace select started failing. Investigate if the change in rendered HTML is expected.
> {code}
> InplaceInputRendererTest.testDefaultWithControlsEncode:29->InplaceRendererTestBase.doTestDefaultWithControlsEncode:29->RendererTestBase.doTest:91->RendererTestBase.checkXmlStructure:114 XML was not similar:org.custommonkey.xmlunit.Diff
> [different] Expected attribute value '/org.richfaces.resources/javax.faces.resource/org.richfaces/ico_ok.gif' but was '/javax.faces.resource/ico_ok.gif.jsf?ln=org.richfaces' - comparing <input src="/org.richfaces.resources/javax.faces.resource/org.richfaces/ico_ok.gif"...> at /span[1]/span[2]/span[1]/span[1]/span[1]/span[5]/input[1]/@src to <input src="/javax.faces.resource/ico_ok.gif.jsf?ln=org.richfaces"...> at /span[1]/span[2]/span[1]/span[1]/span[1]/span[5]/input[1]/@src
> {code}
> {code}
> InplaceSelectRendererTest.testDefaultWithControlsEncode:32->InplaceRendererTestBase.doTestDefaultWithControlsEncode:29->RendererTestBase.doTest:91->RendererTestBase.checkXmlStructure:114 XML was not similar:org.custommonkey.xmlunit.Diff
> [different] Expected attribute value '/org.richfaces.resources/javax.faces.resource/org.richfaces/ico_ok.gif' but was '/javax.faces.resource/ico_ok.gif.jsf?ln=org.richfaces' - comparing <input src="/org.richfaces.resources/javax.faces.resource/org.richfaces/ico_ok.gif"...> at /span[1]/span[2]/span[1]/span[1]/span[1]/span[5]/input[1]/@src to <input src="/javax.faces.resource/ico_ok.gif.jsf?ln=org.richfaces"...> at /span[1]/span[2]/span[1]/span[1]/span[1]/span[5]/input[1]/@src
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months