Hi there,
Are there any plans for a new release of MINA anytime soon? I ask because
we're blocked on Java 10+ support because of
https://issues.apache.org/jira/browse/DIRMINA-1088 which, although fixed,
has yet to be included in a release.
Is there anything we can do to help push a release
That's great, thank you.
Greg
On Tue, 13 Nov 2018 at 22:50, Emmanuel Lecharny
wrote:
> We probably can get a release with only this issue being fixed. I would
> suggest we test it on Java 11 (Java 10 is not going to be supported while
> 11 is LTS).
>
> On Tue, Nov 13, 2018
Brilliant, thanks,
Greg
On Fri, 7 Dec 2018 at 14:05, Emmanuel Lecharny wrote:
> Hi Greg,
>
> I just got a new computer last friday, and I’m unstacking all my backlog
> atm... I’ll check if I can cut a release next week.
>
> Le ven. 7 déc. 2018 à 11:18, Greg Thomas a
while
> 11 is LTS).
>
> On Tue, Nov 13, 2018 at 4:55 PM Greg Thomas
> wrote:
>
> > Hi there,
> >
> > Are there any plans for a new release of MINA anytime soon? I ask because
> > we're blocked on Java 10+ support because of
> > https://issues.apache.o
Thank you!
Greg
On Sun, 24 Feb 2019 at 12:31, Emmanuel Lécharny wrote:
> Hi !
>
>
> I'm closing this vote with 3 binding +1:
>
> Jeff,
>
> Jonathan,
>
> and me.
>
>
> I'm going to push the packages, update the and make the announcement
> this sunday.
>
> I will then cut a 2.1.0 release (I
>
>>> when the data has been fully sent, we go back :
>>>
>>> [Head] --(origMsg)--> [filter] --> ... --(origMsg)--> IoHandler "The
>>> message has been fully sent"
>>>
>>> This original message is likely not to be contained
Openfire - an XMPP server,
https://www.igniterealtime.org/projects/openfire/index.jsp - makes heavy
use of Apache MINA for it's I/O.
One of the things it uses is the CompressionFilter - if clients enable the
Compression XMPP option.
We've recently updated to a newer version of MINA, and with no
:
> Have you pulled a diff between 13 and 14 to try to narrow it down? It’s
> always possible that there is a concurrency problem with compression filter
> which is now exposed through other changes... like what we have with SSL.
>
> On Tue, Mar 19, 2019 at 8:33 AM Greg
:
> I’m trying to look it up in gitbox and it doesn’t show the ids. What was
> the date / first few words of commit message?
>
> On Tue, Mar 19, 2019 at 1:13 PM Greg Thomas
> wrote:
>
> > So just to clarify;
> >
> > If we run against 2.0.14, connections using the
l check if I can cut a release next week.
>
> Le ven. 7 déc. 2018 à 11:18, Greg Thomas a
> écrit :
>
> > Hi,
> >
> > Is there any progress on this? Is there anything we can do to help?
> >
> > Thanks,
> >
> > Greg
> >
> > On Tue, 13
manuel, how do you feel about releasing SNAPSHOT versions? Could the CI
> be configured to do this? This way, we can push to maven and allow
> customers to test the SNAPSHOT versions before moving to releases.
>
>
> On Fri, Feb 1, 2019 at 12:27 PM Greg Thomas
> wrote:
>
>
[
https://issues.apache.org/jira/browse/DIRMINA-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801760#comment-16801760
]
Greg Thomas commented on DIRMINA-1101:
--
Good news; MINA 2.1 seems sufficiently API compatible
[
https://issues.apache.org/jira/browse/DIRMINA-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808721#comment-16808721
]
Greg Thomas commented on DIRMINA-1101:
--
{quote}There is definitively a plan to get a 2.1.1 release
13 matches
Mail list logo
