Re: [VOTE] Release of Trinidad Maven Plugins v. 2.0.7
+1 On Mon, Dec 19, 2011 at 4:00 PM, Dave Robinson drmaill...@gmail.com wrote: +1 On Mon, Dec 19, 2011 at 3:54 PM, Scott O'Bryan darkar...@gmail.comwrote: Hello Everyone, I was running the tasks needed to get the Trinidad Maven Plugins v. 2.0.7 released and now I need a vote as to whether everything looks good or not. There were some minor fixes and the plugins including adding support marking deprecated tag in tag documentation and the removal of some system.out's that made the plugin overly verbose. This tag is needed for the upcoming Trinidad release. I have generated the tag and deployed all the artifacts to the Nexus Repository for review. The artifacts are as follows: * The generated repository artifacts [1] * The updated svn repository [2] Please take a look at the artifacts and don't forget to vote early and often. :D The vote will stay open for at least 72 hours to give people a chance to respond. Thanks, Scott O'Bryan [1] https://repository.apache.org/content/repositories/orgapachemyfaces-004 https://repository.apache.org/content/repositories/orgapachemyfaces-372/ [2] https://svn.apache.org/repos/asf/myfaces/trinidad-maven/tags/maven-plugin-parent-2.0.7https://svn.apache.org/repos/asf/myfaces/trinidad-maven/tags/maven-plugin-parent-2.0.6
Re: [VOTE] Release of Trinidad 2.0.0 Beta 2 (Try 2)
+1
[jira] Created: (TRINIDAD-1888) Need to change log level of partial trigger log message.
Need to change log level of partial trigger log message. Key: TRINIDAD-1888 URL: https://issues.apache.org/jira/browse/TRINIDAD-1888 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.0-alpha-2, 1.2.13-core Reporter: Nathan Hokanson We have a situation where a partial trigger not existing is the correct behavior (in a popup). Because we don't want to fill up the logs with warning messages that are valid, we want to change the log level to info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1888) Need to change log level of partial trigger log message.
[ https://issues.apache.org/jira/browse/TRINIDAD-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Hokanson updated TRINIDAD-1888: -- Status: Patch Available (was: Open) Need to change log level of partial trigger log message. Key: TRINIDAD-1888 URL: https://issues.apache.org/jira/browse/TRINIDAD-1888 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.13-core , 2.0.0-alpha-2 Reporter: Nathan Hokanson Original Estimate: 1h Remaining Estimate: 1h We have a situation where a partial trigger not existing is the correct behavior (in a popup). Because we don't want to fill up the logs with warning messages that are invalid, we want to change the log level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1886) StateManagerImpl.java - popRoot needs to use newInstance in a portlet use case
[ https://issues.apache.org/jira/browse/TRINIDAD-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Hokanson updated TRINIDAD-1886: -- Status: Patch Available (was: Open) StateManagerImpl.java - popRoot needs to use newInstance in a portlet use case -- Key: TRINIDAD-1886 URL: https://issues.apache.org/jira/browse/TRINIDAD-1886 Project: MyFaces Trinidad Issue Type: Bug Components: Portlet Affects Versions: 1.2.12-core, 2.0.0-alpha Environment: portlet, any OS Reporter: Nathan Hokanson Attachments: trinidad-1886.1.2.12.3-branch.patch, trinidad-1886.trunk.patch The StateManagerImpl$PageState.popRoot method uses the PortletUtils.getPortletViewRoot method to wrap the root object when in a Portlet use case. This causes errors in some bridges because the object returned form the utility method may not be the same as the one injected as the viewRoot by the bridge. The fix is to mimic the RI (Mojarra) to call newInstance on the root returned from the application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1886) StateManagerImpl.java - popRoot needs to use newInstance in a portlet use case
StateManagerImpl.java - popRoot needs to use newInstance in a portlet use case -- Key: TRINIDAD-1886 URL: https://issues.apache.org/jira/browse/TRINIDAD-1886 Project: MyFaces Trinidad Issue Type: Bug Components: Portlet Affects Versions: 2.0.0-alpha, 1.2.12-core Environment: portlet, any OS Reporter: Nathan Hokanson The StateManagerImpl$PageState.popRoot method uses the PortletUtils.getPortletViewRoot method to wrap the root object when in a Portlet use case. This causes errors in some bridges because the object returned form the utility method may not be the same as the one injected as the viewRoot by the bridge. The fix is to mimic the RI (Mojarra) to call newInstance on the root returned from the application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (PORTLETBRIDGE-56) IllegalStateException thrown during getClientId call.
IllegalStateException thrown during getClientId call. - Key: PORTLETBRIDGE-56 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-56 Project: MyFaces Portlet Bridge Issue Type: Bug Components: General Affects Versions: 1.0.0-alpha-3 Reporter: Nathan Hokanson If the getClientId is called during the ActionRequest, an IlleagalStateException is thrown because the getClientId method of PortletNamingContainerUIViewRoot attempts to call ExternalContext.encodeNamespace(), even during the action request. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1351) On a redirect the URL is not being properly encoded for portals.
On a redirect the URL is not being properly encoded for portals. Key: TRINIDAD-1351 URL: https://issues.apache.org/jira/browse/TRINIDAD-1351 Project: MyFaces Trinidad Issue Type: Bug Components: Portlet Affects Versions: 1.2.10-core Environment: JSR 168, Portlet Bridge, JSF Reporter: Nathan Hokanson In certain navigation use cases where a JSF resource is being requested, the redirect url is not being encoded. This causes the render kit to pop the user out of the portlet environment and back into the basic servlet env. This fix will not affect the servlet case since url encoding is passive when not in a portlet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1351) On a redirect the URL is not being properly encoded for portals.
[ https://issues.apache.org/jira/browse/TRINIDAD-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Hokanson updated TRINIDAD-1351: -- Status: Patch Available (was: Open) On a redirect the URL is not being properly encoded for portals. Key: TRINIDAD-1351 URL: https://issues.apache.org/jira/browse/TRINIDAD-1351 Project: MyFaces Trinidad Issue Type: Bug Components: Portlet Affects Versions: 1.2.10-core Environment: JSR 168, Portlet Bridge, JSF Reporter: Nathan Hokanson Attachments: Trinidad-1351.patch Original Estimate: 1h Remaining Estimate: 1h In certain navigation use cases where a JSF resource is being requested, the redirect url is not being encoded. This causes the render kit to pop the user out of the portlet environment and back into the basic servlet env. This fix will not affect the servlet case since url encoding is passive when not in a portlet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
