Re: MINA release error...

2018-06-11 Thread Jonathan Valliere
Should be fine; ApacheDS is a complex project that used hooks for the old SSL Events to listen when SSL was started / ended. On Mon, Jun 11, 2018 at 5:18 AM, Christoph John wrote: > Hi Emmanuel, > > just a short question: I can compile against 2.0.18 without problems and > the tests run fine. So

Re: MINA release error...

2018-06-11 Thread Christoph John
Thanks for the information. No problem, will wait then. Chris. On 11/06/18 11:54, Emmanuel Lécharny wrote: Le 11/06/2018 à 11:18, Christoph John a écrit : Hi Emmanuel, just a short question: I can compile against 2.0.18 without problems and the tests run fine. So is it safe to use that versi

Re: MINA release error...

2018-06-11 Thread Emmanuel Lécharny
Le 11/06/2018 à 11:18, Christoph John a écrit : > Hi Emmanuel, > > just a short question: I can compile against 2.0.18 without problems and > the tests run fine. So is it safe to use that version then? In our > project we extend AbstractIoHandler. So it's safe. 2.0.19 fixed the API regressions

Re: MINA release error...

2018-06-11 Thread Christoph John
Hi Emmanuel, just a short question: I can compile against 2.0.18 without problems and the tests run fine. So is it safe to use that version then? In our project we extend AbstractIoHandler. Thanks and cheers, Christoph. On 07/06/18 20:13, Emmanuel Lécharny wrote: Hi guys, I have made a mis

Re: MINA release error...

2018-06-07 Thread Emmanuel Lécharny
Le 07/06/2018 à 20:41, Jonathan Valliere a écrit : > Would it make sense to rename the 3.0 branch to FUTURE or something that > doesn’t involve a numerical version number? Sure. It's a bit annoying to have blocked a version number for years... -- Emmanuel Lecharny Symas.com directory.apache.

Re: MINA release error...

2018-06-07 Thread Jonathan Valliere
Would it make sense to rename the 3.0 branch to FUTURE or something that doesn’t involve a numerical version number? On Thu, Jun 7, 2018 at 2:13 PM, Emmanuel Lécharny wrote: > Hi guys, > > I have made a mistake when I cut the latest release (MINA 2.0.18), which > breaks the API - actually, two e