Awesome JL.
Do you have some details about the breaking changes?
Le mar. 24 sept. 2019 à 03:51, Jean-Louis Monteiro
a écrit :
> All right, created this one for health
> https://issues.apache.org/jira/browse/GERONIMO-6752
> I have a fix for a bug in the way we handle producer
>
All right, created this one for health
https://issues.apache.org/jira/browse/GERONIMO-6752
I have a fix for a bug in the way we handle producer
https://issues.apache.org/jira/browse/GERONIMO-6753
Since we upgraded to health 2.0 and there are some breaking changes, I have
bumped up the version to
I have opened this ticket and pushed a fix on both Java EE 7 and 8 API jar.
New snapshot deployed.
I'm waiting for the full build on master to pass and then I'll close the
ticket and fire up the 2 releases so you can move on with TomEE
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
Oh wow, that would be amazing!
On Mon, Sep 23, 2019 at 10:49 PM Jonathan S. Fisher
wrote:
> I'll get a reproducer project put together that demos the bug.
>
> On Mon, Sep 23, 2019 at 4:32 PM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
>
> > If we can come up with some good tests
I'll get a reproducer project put together that demos the bug.
On Mon, Sep 23, 2019 at 4:32 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> If we can come up with some good tests for it, I don't see why not.
>
> Jon
>
> On Mon, Sep 23, 2019 at 10:25 PM Jonathan S. Fisher
> wrote:
If we can come up with some good tests for it, I don't see why not.
Jon
On Mon, Sep 23, 2019 at 10:25 PM Jonathan S. Fisher
wrote:
> We've been running 7.0.x latest in prod for a few weeks with no issues
> other than the ActiveMQ Failover protocol memory leak issue (which affects
> all
We've been running 7.0.x latest in prod for a few weeks with no issues
other than the ActiveMQ Failover protocol memory leak issue (which affects
all versions of TomEE).
https://issues.apache.org/jira/browse/AMQ-6391 This is an issue now because
our JMS Context / Connection Factories will actually
The Locator issue raised earlier today. Would be great to get the fix in
before rolling.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Mon, Sep 23, 2019 at 12:33 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> I'm just doing some cleanup on
I'm just doing some cleanup on these branches. I'm thinking its
probably time we put out new releases as these branches have seen some
fixes.
Is there anything that we think is missing before I kick off some releases
and votes?
I'd like to get the quartz-openejb-shade update if possible - that
Bumping this one up - this addresses a CVE (CVE-2019-13990 -
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13990), and it
would be good to release unless there are issues with it.
Thanks
Jon
On Mon, Sep 9, 2019 at 4:58 PM Jean-Louis Monteiro
wrote:
> Looks good.
> +1
> --
>
I suggest sticking to semvar as much as possible. So an intentional API
break change should be 9.x.x in that case. For Jakarta EE compliance work,
8.1.x would be my vote, as the changes should be backward compatible.
On Sun, Sep 22, 2019 at 6:48 PM David Blevins
wrote:
> We need to do some
Hi JL
AFAIK the missing impl are mainly fault tolerance 2 (which adds
completionstage support we already have), opentracing 1.3 (which is sadly
just minor fixes compared to others and no opentracing upgrade IIRC), and
metrics 2 (which mainly split counters in 2 entities). Other specs are
ready I
12 matches
Mail list logo
