I'm only experiencing this now, otherwise I would have spoken up earlier.
This is a backwards-incompatible change of a public API.
Although the fix is trivial it needs to be documented. We (Tapestry devs)
probably didn't encounter
it earlier because we rely on EnumValueEncoderFactory internally,
On Wed, Jan 18, 2012 at 8:27 PM, Luca Menegus wrote:
> I found it today, tomorrow I will check all the Italian localization and
> provide a patch (hope I'm not late).
I'll check this.
Cheers
--
Massimo
http://meridio.blogspot.com
--
My suggestions (I've also rephrased other messages to make them more fluent):
Index:
tapestry-core/src/main/resources/org/apache/tapestry5/internal/ValidationMessages_it.properties
===
---
tapestry-core/src/main/resources/org/apache
Well, perhaps the right approach would have been to deprecate the
existing class and introduce a EnumValueEncoder2 that uses the
TypeCoercer.
On Thu, Jan 19, 2012 at 6:51 AM, Ulrich Stärk wrote:
> I'm only experiencing this now, otherwise I would have spoken up earlier.
>
> This is a backwards-in
