I spent some time last night testing it for my needs, and everything seemed to work fine.
It did, however, break one of my plugins that uses the xwork UrlSet class, whose constructor signatures have changed in this release, breaking my code. Was there a reason the constructor couldn't have been marked deprecated instead of completely removed, so that this sort of change doesn't completely break custom plugins? Not a big deal, though. The class isn't part of the API really, so I should have no expectation of it not changing. Rees On Sat, Oct 27, 2012 at 9:47 AM, Lukasz Lenart <[email protected]>wrote: > Ping :-) Anyone can help and test the test build! > > L. > > 2012/10/23 Lukasz Lenart <[email protected]>: > > Hi all, > > > > A new version of Struts 2.3.6 is coming, please take a time and test > > the bits [1] or use Maven staging repository [2]. Please refer to > > Version Notes [3] for more details what was changed. > > > > If there be no show-stoppers I'm going to call for a Vote in a week. > > > > [1] http://people.apache.org/builds/struts/2.3.6/ > > [2] https://repository.apache.org/content/groups/staging/ > > [3] https://cwiki.apache.org/WW/version-notes-236.html > > > > > > Kind regards > > -- > > Łukasz > > mobile +48 606 323 122 http://www.lenart.org.pl/ > > Warszawa JUG conference - Confitura http://confitura.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
