Guys,
the wikidocs export seems to be missing both in the struts-2.1.6-all.zip
struts-2.1.6-docs.zip. The good news is that this does not mean that a
new release process has to be triggered afaik, since these are artifacts
which can be changed easily before final distribution (which is not the
case for maven artifacts). This should really be fixed before release.
Minor findings in showcase:
- token example 3 (token-session based .jsp example) fails, while 4
(fremarker) works fine
- field Validators with client-side JavaScript does no client side
validation, same with Validation (client) and Validation (client using
css_xhtml theme) (tested with Glassfish V2 / Firefox 3 / Ubuntu Hardy)
- Person Manager / create person is broken
Most of the these are good to fix in next relase, only the client
validation stuff might be a stopping reason. Maybe someone could
crosscheck - if it's broken in general, we should think of fixing it
before a release.
I think we also need a nice and handy "press compatible" release note,
which gives a good overview on 2.1 enhancements over 2.0 and why this
makes it the #1, most advanced action framework available :)
So far for now,
- Rene
Musachy Barroso schrieb:
The Struts 2.1.6 test build is now available.
Release notes:
* [http://struts.apache.org/2.x/docs/version-notes-216.html]
Distribution:
* [http://people.apache.org/builds/struts/2.1.6/]
Maven 2 staging repository:
* [http://people.apache.org/builds/struts/2.1.6/m2-staging-repository/]
Once you have had a chance to review the test build, please respond
with a vote on its quality:
[ ] Leave at test build
[ ] Alpha
[ ] Beta
[ ] General Availability (GA)
Everyone who has tested the build is invited to vote. Votes by PMC
members are considered binding. A vote passes if there are at least
three binding +1s and more +1s than -1s.
The vote will remain open for at least 72 hours, longer upon request.
A vote can be amended at any time to upgrade or downgrade the quality
of the release based on future experience. If an initial vote
designates the build as "Beta", the release will be submitted for
mirroring and announced to the user list. Once released as a public
beta, subsequent quality votes on a build may be held on the user
list.
As always, the act of voting carries certain obligations. A binding
vote not only states an opinion, but means that the voter is agreeing
to help do the work
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
