Any chance we can sneek the freemarker update in as well. It seems to be showing improvements to performance in multi-client cases without any negative side effects.

Al.

Don Brown wrote:
2.0.11.3 sounds fine to me.  Are there that many commits on the 2.0.x
branch that we aren't ready to release?

Don

On Tue, Jul 8, 2008 at 10:07 AM, Rene Gielen <[EMAIL PROTECTED]> wrote:
Some might have noticed that there was still no official announcement
for 2.0.11.2 availability. Until Saturday, there was an issue with the
gpg signature of the maven artifacts [1], which needed a pom fix [2] and
a redeployment of the files to sync with the official maven
repositories. Since Saturday, correctly signed artifacts should be
distributed.

Just before I wanted to get the announcement out on Sunday, a possibly
blocking issue for 2.0.11.2 users under Websphere 6 was reported [3]. It
turned out that the issue was already known and fixed for Struts 2.1.x /
XWork 2.1.x, but the critical patch already applied in XWork2 trunk was
not in the 2.0 branch, causing 2.0.5 to break in a Websphere
environment. The fix is applied now [4], but it looks like this is to
late for the 2.0.11.2 release.

The cleanest solution is to release a XWork 2.0.6 including the fix, and
a Struts 2.0.12.3 release still under fast track conditions. Do we have
better / faster options? Comments highly appreciated...

[1] http://people.apache.org/~henkp/repo/
[2] http://people.apache.org/~henkp/repo/faq.html
[3] https://issues.apache.org/struts/browse/WW-2709
[4] http://jira.opensymphony.com/browse/XW-651

Rene Gielen schrieb:
+1 GA binding

 * Rene Gielen
 * Rainer Hermanns
 * Musachy Barroso

+1 GA supporting

 * Dave Newton

Struts 2.0.11.2 is now rated at GA, and I proceeded to copying the
files for mirroring. After veryfing, I'll post the announcement.

Regards,
Rene

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

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



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



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

Reply via email to