ISTR someone saying it seemed like it would be safe to make this break in BC because there were likely to be no existing FastDateParser subclasses. However, the compatibility was preserved in FastDateFormat by passing through a null *to* FastDateParser, so doing the same on FastDateParser itself would seem simple and equivalent.
Matt On Thu, Feb 27, 2014 at 1:45 PM, Gary Gregory <garydgreg...@gmail.com>wrote: > Can we add back a ctor? > > Gary > > > On Thu, Feb 27, 2014 at 10:37 AM, Benedikt Ritter <brit...@apache.org > >wrote: > > > Hi, > > > > I'm preparing lang 3.3 RC 1. While looking through the reports I've > > noticed, that we have a Clirr error in 3.3 compared to 3.2.1 [1]. This > was > > introduced in r1557882 [2]. The change is a result of LANG-950 [3] > > > > The question for me is: can we handle this change without breaking BC? > > > > Benedikt > > > > [1] > http://people.apache.org/~britter/commons-sites/lang/clirr-report.html > > [2] http://svn.apache.org/r1557882 > > [3] https://issues.apache.org/jira/browse/LANG-950 > > > > -- > > http://people.apache.org/~britter/ > > http://www.systemoutprintln.de/ > > http://twitter.com/BenediktRitter > > http://github.com/britter > > > > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition< > http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory >
