+1

 

 

-- 

Steve Milek

Bluesunrise Software

[EMAIL PROTECTED]

[mobile] +01 303 408-1223

 

 

 

On Jul 8, 2007, at 8:43 PM, Ate Douma wrote:

 

A Bridges 1.0.2 build has been cut and is available as indicated below.

 

The Bridges team considers this a quality build which we're proposing for GA
release.

 

The results of this vote will be posted no earlier than 72 hours from the
time this email is sent.

3 +1 votes from Apache Portals PMC members will be required to meet quorum,
but all community members (committers, contributors, and users) are invited
to vote. We welcome any comments you may have, and will take all feedback
into account.

 

Distribution:

 

* http://people.apache.org/~ate/bridges-1.0.2.tar.gz

 

Release Notes - Portals Bridges - Version 1.0.2

 

** Sub-task

* [PB-25] - Provide bridges library components build configuration and xdocs

 

** Bug

* [PB-7] - Messages are not displayed, validation errors are ignored

* [PB-58] - PHP bridge: bug in ServletConfigImpl

* [PB-59] - Struts bridge: render phase of portlet doesn't remove the attr
RENDER_CONTEXT from the portlet session

* [PB-64] - FacesPortlet should Restore View before the ActionRequest
lifecycle is executed.

* [PB-66] - FacesPortlet should apply defaultRenderKitId instead of
HTML_BASIC

* [PB-68] - PortletUIViewRoot needs saveState

 

** Improvement

* [PB-63] - Update to latest dependencies

* [PB-67] - Added support for ServletRequests

* [PB-69] - Groovy Portlet Bridge for rapid dev: Parse, instantiate, invoke
and auto-refresh a groovy script portlet

* [PB-70] - Groovy Bridge needs to support groovy script preferences
validator and groovy script pre-286 portlet.

 

** New Feature

* [PB-65] - PortletResourceURLFactory: A new generic interface for direct
access to a portlet, a lightweight version of what Portlet 2.0 ResourceURL
will provide

 

 

---------------------------------------------------------------------

To unsubscribe, e-mail: [EMAIL PROTECTED]

For additional commands, e-mail: [EMAIL PROTECTED]

 

 

Reply via email to