You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Emmanuel Lécharny <el...@gmail.com> on 2018/06/07 18:13:59 UTC
MINA release error...
Hi guys,
I have made a mistake when I cut the latest release (MINA 2.0.18), which
breaks the API - actually, two errors -.
The first one was to inject a new event in the IoHandler, expecting
users to extend IoHandlerAdapter instead of implementing IoHandler
The second one was related to the removal of 2 messages (SESSION_SECURED
and SESSION_UNSECURED). That was due to a big commit that included those
changes, which weren't expected to be applied immediately.
In order to fix this breakage, here is what I'll do :
- first cut a 2.0.19 that is compatible with teh 2.0.17 API, in order to
have the application dependning on this API to work without any change
- and second cut a 2.1.0 with all the changes.
In the short term, both versions will be maintained, in teh long run,
2.1 will be the new maintained version.
There is still a 3.0.0 branch that require some love, for the record :-)
Sorry for the mess...
--
Emmanuel Lecharny
Symas.com
directory.apache.org
Re: MINA release error...
Posted by Emmanuel Lécharny <el...@gmail.com>.
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.org
Re: MINA release error...
Posted by Jonathan Valliere <jo...@apache.org>.
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 <el...@gmail.com>
wrote:
> Hi guys,
>
> I have made a mistake when I cut the latest release (MINA 2.0.18), which
> breaks the API - actually, two errors -.
>
> The first one was to inject a new event in the IoHandler, expecting
> users to extend IoHandlerAdapter instead of implementing IoHandler
>
> The second one was related to the removal of 2 messages (SESSION_SECURED
> and SESSION_UNSECURED). That was due to a big commit that included those
> changes, which weren't expected to be applied immediately.
>
>
> In order to fix this breakage, here is what I'll do :
>
> - first cut a 2.0.19 that is compatible with teh 2.0.17 API, in order to
> have the application dependning on this API to work without any change
>
> - and second cut a 2.1.0 with all the changes.
>
> In the short term, both versions will be maintained, in teh long run,
> 2.1 will be the new maintained version.
>
> There is still a 3.0.0 branch that require some love, for the record :-)
>
> Sorry for the mess...
>
> --
> Emmanuel Lecharny
>
> Symas.com
> directory.apache.org
>
>
Re: MINA release error...
Posted by Jonathan Valliere <jo...@apache.org>.
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 <ch...@macd.com>
wrote:
> 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 mistake when I cut the latest release (MINA 2.0.18), which
>> breaks the API - actually, two errors -.
>>
>> The first one was to inject a new event in the IoHandler, expecting
>> users to extend IoHandlerAdapter instead of implementing IoHandler
>>
>> The second one was related to the removal of 2 messages (SESSION_SECURED
>> and SESSION_UNSECURED). That was due to a big commit that included those
>> changes, which weren't expected to be applied immediately.
>>
>>
>> In order to fix this breakage, here is what I'll do :
>>
>> - first cut a 2.0.19 that is compatible with teh 2.0.17 API, in order to
>> have the application dependning on this API to work without any change
>>
>> - and second cut a 2.1.0 with all the changes.
>>
>> In the short term, both versions will be maintained, in teh long run,
>> 2.1 will be the new maintained version.
>>
>> There is still a 3.0.0 branch that require some love, for the record :-)
>>
>> Sorry for the mess...
>>
>>
> --
> Christoph John
> Software Engineering
> T +49 241 557080-28
> christoph.john@macd.com
>
> MACD GmbH
> Oppenhoffallee 103
> 52066 Aachen, Germany
> www.macd.com
>
> Amtsgericht Aachen: HRB 8151
> Ust.-Id: DE 813021663
> Geschäftsführer: George Macdonald
>
>
Re: MINA release error...
Posted by Christoph John <ch...@macd.com>.
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 version then? In our
>> project we extend AbstractIoHandler.
> So it's safe.
>
> 2.0.19 fixed the API regressions (removing the event() method from the
> IoHandler, sending SESSION_SECURED message) and that's all.
>
> 2.0.19 will be released today, so if you can wait a few hours, it's
> probably good too.
>
>
--
Christoph John
Software Engineering
T +49 241 557080-28
christoph.john@macd.com
MACD GmbH
Oppenhoffallee 103
52066 Aachen, Germany
www.macd.com
Amtsgericht Aachen: HRB 8151
Ust.-Id: DE 813021663
Geschäftsführer: George Macdonald
Re: MINA release error...
Posted by Emmanuel Lécharny <el...@gmail.com>.
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 (removing the event() method from the
IoHandler, sending SESSION_SECURED message) and that's all.
2.0.19 will be released today, so if you can wait a few hours, it's
probably good too.
--
Emmanuel Lecharny
Symas.com
directory.apache.org
Re: MINA release error...
Posted by Christoph John <ch...@macd.com>.
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 mistake when I cut the latest release (MINA 2.0.18), which
> breaks the API - actually, two errors -.
>
> The first one was to inject a new event in the IoHandler, expecting
> users to extend IoHandlerAdapter instead of implementing IoHandler
>
> The second one was related to the removal of 2 messages (SESSION_SECURED
> and SESSION_UNSECURED). That was due to a big commit that included those
> changes, which weren't expected to be applied immediately.
>
>
> In order to fix this breakage, here is what I'll do :
>
> - first cut a 2.0.19 that is compatible with teh 2.0.17 API, in order to
> have the application dependning on this API to work without any change
>
> - and second cut a 2.1.0 with all the changes.
>
> In the short term, both versions will be maintained, in teh long run,
> 2.1 will be the new maintained version.
>
> There is still a 3.0.0 branch that require some love, for the record :-)
>
> Sorry for the mess...
>
--
Christoph John
Software Engineering
T +49 241 557080-28
christoph.john@macd.com
MACD GmbH
Oppenhoffallee 103
52066 Aachen, Germany
www.macd.com
Amtsgericht Aachen: HRB 8151
Ust.-Id: DE 813021663
Geschäftsführer: George Macdonald