Only if the compatibility issue can be fixed. I don't think it can. We will
just update the site and announcement.
Sent from my iPhone
> On May 29, 2016, at 10:56 AM, Matt Sicker <boa...@gmail.com> wrote:
>
> So what do we do, follow up with 2.6.1 right away?
>
>> On 29 May 2016 at 12:29, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>> Can’t do that. That would require a re-release.
>>
>> Speaking of which, the archives directory only lists a couple of releases. I
>> thought they were all supposed to be there.
>>
>> Ralph
>>
>>> On May 29, 2016, at 10:19 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
>>>
>>> I think the RELEASE-NOTES.txt in the dist area needs to be updated as well.
>>>
>>> Gary
>>>
>>>> On Sun, May 29, 2016 at 10:15 AM, Ralph Goers <ralph.go...@dslextreme.com>
>>>> wrote:
>>>> I will add something to the announcement text when I send out the emails.
>>>> Those will go out in a few hours.
>>>>
>>>> Ralph
>>>>
>>>>> On May 29, 2016, at 9:53 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
>>>>>
>>>>> We are going to need to update the release notes and/or site for 2.6 to
>>>>> note that the 2.6 is not source compatible with previous releases. I
>>>>> tested going from 2.5 to 2.6 at work and got:
>>>>>
>>>>> [ERROR] COMPILATION ERROR :
>>>>> [INFO] -------------------------------------------------------------
>>>>> [ERROR] /E:/vcs/svn/...XYZ..:[155,15] reference to error is ambiguous
>>>>> both method
>>>>> error(org.apache.logging.log4j.Marker,java.lang.String,java.lang.Object)
>>>>> in org.apache.logging.log4j.Logger and method
>>>>> error(java.lang.String,java.lang.Object,java.lang.Object) in
>>>>> org.apache.logging.log4j.Logger match
>>>>> [ERROR] /E:/vcs/svn/...XYZ...:[395,15] reference to trace is ambiguous
>>>>> both method
>>>>> trace(org.apache.logging.log4j.Marker,java.lang.String,java.lang.Object)
>>>>> in org.apache.logging.log4j.Logger and method
>>>>> trace(java.lang.String,java.lang.Object,java.lang.Object) in
>>>>> org.apache.logging.log4j.Logger match
>>>>> [INFO] 2 errors
>>>>>
>>>>> with source code like:
>>>>>
>>>>> public void xyz(final String message, final Throwable t) {
>>>>> ...
>>>>> logger.error(null, message, t);
>>>>> ...
>>>>> logger.trace(null, message, t);
>>>>> ...
>>>>> }
>>>>>
>>>>> Next time, I'll remember to test with a "real" client.
>>>>>
>>>>> Gary
>>>>>
>>>>> --
>>>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>>>> Java Persistence with Hibernate, Second Edition
>>>>> JUnit in Action, Second Edition
>>>>> Spring Batch in Action
>>>>> Blog: http://garygregory.wordpress.com
>>>>> Home: http://garygregory.com/
>>>>> Tweet! http://twitter.com/GaryGregory
>>>
>>>
>>>
>>> --
>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> JUnit in Action, Second Edition
>>> Spring Batch in Action
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>
>
>
> --
> Matt Sicker <boa...@gmail.com>
