Re: Buildbot slowness

Building is not a problem, it's the CDI TCK test run causing out of memory exception in tomee -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Building with Java 11

Seems that we need dependencies update on mockito module. I was getting java.lang.NoClassDefFoundError for JAXB class and some error on Mockito API. Em sex, 1 de mar de 2019 às 18:30, Jonathan Gallimore < jonathan.gallim...@gmail.com> escreveu: > Definitely slow - same issue as master on the CI

Re: Buildbot slowness

Hi folks, it is happening in a specif module? I'm building tomee without samples and seems fine to me. mvn clean install -Pquick Em sáb, 2 de mar de 2019 às 00:36, j4fm escreveu: > Hey Jon, thanks for the test. Do you still have all my PRs in there after > just removing the PR409? > > Yeah,

Re: Buildbot slowness

Hey Jon, thanks for the test. Do you still have all my PRs in there after just removing the PR409? Yeah, I was looking around all the dependency changes that CXF (and JAXB which it depends on) brings in. I do have something I am working on, instead of excluding the older javax conflicting

Re: Buildbot slowness

Thanks for the update James. I reverted locally: https://github.com/apache/tomee/pull/409 , build tome without tests and then: mvn -pl tck/cdi-tomee --fail-at-end -Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8 clean install -Pall-adapters -Dsurefire.useFile=false -DdisableXmlReport=true

Re: Buildbot slowness

False fix, it just got a lot further before an oom exception. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Buildbot slowness

I have a fix for the slow build (works locally without memory error now). If somebody wouldn't mind stopping the current buildbot task and I will create a small PR. Thanks in advance -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Buildbot slowness

Not sure it's ever going to finish. Seems to be grinding to a halt. You're right, no point letting it run. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Buildbot slowness

Would like to get the stats at the end of the CI build if possible too. PR409 was the first merge to start the issue but there are no code changes in there except to examples and the bumps of CXF and JAXB. Do you see it just being cdi-tomee that's slowed up? I'm checking out it's (indirect)

Re: Buildbot slowness

Waiting on my machine to crunch some numbers, but here's the summary: Total Bytes: 2,726,889,443 Total Classes: 124,138 Total Instances: 54,413,232 Classloaders: 790 GC Roots: 3,842 Number of Objects Pending for Finalization: 0 That seems like a lot of

Re: Buildbot slowness

On the plus side, I have a heap dump here, so we can take a look. Jon On Fri, Mar 1, 2019 at 9:28 PM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > Seeing the same with the java11-experimentation build here: > > # Created on 2019-03-01T18:01:43.414 > Corrupted STDOUT by directly

Re: Apache TomEE channel in the-asf.slack.com

Me also On Fri, Mar 1, 2019 at 2:28 PM Gabriel Ferreira wrote: > If possible, I'd like an invitation too. ;) > > Em sex, 1 de mar de 2019 às 16:30, David Blevins > escreveu: > > > Some time ago even the ASF Infra team stopped using IRC. They now use > > Slack and there is an "official" ASF

Re: Building with Java 11

Definitely slow - same issue as master on the CI by the look of it. Jon On Fri, Mar 1, 2019 at 9:23 PM j4fm wrote: > Do you have any idea if you J11 branch build is slow vs normal just yet? > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >

Re: Buildbot slowness

Seeing the same with the java11-experimentation build here: # Created on 2019-03-01T18:01:43.414 Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream 'java.lang.OutOfMemoryError: Java heap space'. java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma

Re: Building with Java 11

Do you have any idea if you J11 branch build is slow vs normal just yet? -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Buildbot slowness

Getting this WARNING on :cdi-tomee on buildbot which is taking forever... # Created on 2019-03-01T20:48:20.010 Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream 'java.lang.OutOfMemoryError: Java heap space'. java.lang.IllegalArgumentException: Stream stdin corrupted.

Buildbot slowness

Buildbot is slow with :cdi-tomee tests causing out of memory warnings. The PR409 (CXF 3.3.0 and JAXB 2.3.2) updates was the first merge to cause the slowness. The rolled up merges after show the same. # Created on 2019-03-01T20:48:20.010 Corrupted STDOUT by directly writing to native stream in

Re: Apache TomEE channel in the-asf.slack.com

Done On Fri, Mar 1, 2019 at 5:54 PM j4fm wrote: > Me too please > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >

Re: Building with Java 11

Started a new thread for slowness... the warnings are out of memory. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Building with Java 11

That makes sense, just didn't want to confuse the j11 branch test failures vs what could be causing the slowness. I'm seeing those same warnings now locally so I can try and dig deeper here. :) -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Building with Java 11

The build of the java11-experimentation branch (on Java 8) is running on a box here in my office. "Normally" a build of master on that box takes ~ 2 to 2.5 hours. The failures I listed are for that build. The build on the Apache CI is master. Recent builds on that node seem to be the same length

Re: Apache TomEE channel in the-asf.slack.com

Me too please -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Building with Java 11

The tests you copied out do not look like they failed on buildbot or locally. There are no failures so far and it's quite far along. It's appears to just be slow. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Building with Java 11

PR409 was the merge that was first seen being slow. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Building with Java 11

My Java 8 build is still running here. Its currently on the CDI TCK, and so far 4 reported test failures: [ERROR] run(org.apache.openejb.resource.activemq.ProperConnectionShutdownTest) Time elapsed: 3.295 s <<< FAILURE! org.superbiz.executor.ManagedScheduledServiceTest Time elapsed: 3.872 sec

Re: Building with Java 11

Hi, the last build Jonathan started is still running after 3hrs. 30 min: https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/1048 Can some committer please trigger a build for master branch to compare and check James observation? El vie., 1 mar. 2019 a las 14:39, j4fm () escribió: >

Re: Building with Java 11

Thanks Jon, so it wasn't frozen (impatient me) - just mid-test but running like someone stole it's ponies. Once it finishes I will check the stats, but did you see slowness happen before... could it be busy infra? -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Apache TomEE channel in the-asf.slack.com

I'd like an invitation too. El vie., 1 mar. 2019 a las 14:28, Gabriel Ferreira () escribió: > If possible, I'd like an invitation too. ;) > > Em sex, 1 de mar de 2019 às 16:30, David Blevins > escreveu: > > > Some time ago even the ASF Infra team stopped using IRC. They now use > > Slack and

Re: Apache TomEE channel in the-asf.slack.com

If possible, I'd like an invitation too. ;) Em sex, 1 de mar de 2019 às 16:30, David Blevins escreveu: > Some time ago even the ASF Infra team stopped using IRC. They now use > Slack and there is an "official" ASF Slack group. I asked if it was ok if > projects could create themselves a

Re: Building with Java 11

If that's just for itests, I'd be inclined to try creating a profile to add that where the Java version is >8. What do you think? Jon On Fri, Mar 1, 2019 at 6:16 PM Otávio Gonçalves de Santana < osant...@tomitribe.com> wrote: > Hey guys > > I'm working to make the tests compatible with both

Re: Apache TomEE channel in the-asf.slack.com

Hi folks, Can you please send me an invite too? Cheers Bruno Baptista http://twitter.com/brunobat_ > On 1 Mar 2019, at 19:52, Ivan Junckes Filho wrote: > > It seems it forces you to have a apache email or to be invited. I can't > join, can anyone invite me? > >> On Fri, Mar 1, 2019 at 4:51 PM

Re: Apache TomEE channel in the-asf.slack.com

Thanks Otavio, it worked. On Fri, Mar 1, 2019 at 4:56 PM Otávio Gonçalves de Santana < osant...@tomitribe.com> wrote: > Hey Ivan, done > > On Fri, Mar 1, 2019 at 4:52 PM Ivan Junckes Filho > wrote: > > > It seems it forces you to have a apache email or to be invited. I can't > > join, can

Re: Apache TomEE channel in the-asf.slack.com

Hey Ivan, done On Fri, Mar 1, 2019 at 4:52 PM Ivan Junckes Filho wrote: > It seems it forces you to have a apache email or to be invited. I can't > join, can anyone invite me? > > On Fri, Mar 1, 2019 at 4:51 PM Daniel Cunha wrote: > > > Hi Gabriel, > > > > Yes! > > > > Em sex, 1 de mar de 2019

Re: Apache TomEE channel in the-asf.slack.com

It seems it forces you to have a apache email or to be invited. I can't join, can anyone invite me? On Fri, Mar 1, 2019 at 4:51 PM Daniel Cunha wrote: > Hi Gabriel, > > Yes! > > Em sex, 1 de mar de 2019 às 16:48, Gabriel Ferreira > escreveu: > > > Cool, can everyone on the list participate? >

Re: Apache TomEE channel in the-asf.slack.com

Hi Gabriel, Yes! Em sex, 1 de mar de 2019 às 16:48, Gabriel Ferreira escreveu: > Cool, can everyone on the list participate? > > Em sex, 1 de mar de 2019 às 16:30, David Blevins > escreveu: > > > Some time ago even the ASF Infra team stopped using IRC. They now use > > Slack and there is an

Re: Apache TomEE channel in the-asf.slack.com

yes -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Fri, Mar 1, 2019 at 8:48 PM Gabriel Ferreira wrote: > Cool, can everyone on the list participate? > > Em sex, 1 de mar de 2019 às 16:30, David Blevins > escreveu: > > > Some time ago even the ASF Infra

Re: Apache TomEE channel in the-asf.slack.com

Cool, can everyone on the list participate? Em sex, 1 de mar de 2019 às 16:30, David Blevins escreveu: > Some time ago even the ASF Infra team stopped using IRC. They now use > Slack and there is an "official" ASF Slack group. I asked if it was ok if > projects could create themselves a

Re: Apache TomEE channel in the-asf.slack.com

Thanks for the info David. I'm there. :) Em sex, 1 de mar de 2019 às 16:30, David Blevins escreveu: > Some time ago even the ASF Infra team stopped using IRC. They now use > Slack and there is an "official" ASF Slack group. I asked if it was ok if > projects could create themselves a channel

Apache TomEE channel in the-asf.slack.com

Some time ago even the ASF Infra team stopped using IRC. They now use Slack and there is an "official" ASF Slack group. I asked if it was ok if projects could create themselves a channel and they said, "sure!" Here it is! - https://the-asf.slack.com/messages/CGN2PPR55 I invite everyone

Re: Building with Java 11

Nice, thanks for looking at that! On Fri, 1 Mar 2019, 18:16 Otávio Gonçalves de Santana, < osant...@tomitribe.com> wrote: > Hey guys > > I'm working to make the tests compatible with both Java 8 and Java 11 > version. > > > Right now, I'm at the failover >

Re: Building with Java 11

Hey guys I'm working to make the tests compatible with both Java 8 and Java 11 version. Right now, I'm at the failover project that has this issue: java.lang.IllegalAccessException: class org.apache.openejb.loader.BasicURLClassPath

Re: Building with Java 11

Killed of the builds and forced a new one. https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/1048 Jon On Fri, Mar 1, 2019 at 4:28 PM j4fm wrote: > Ah yeah that makes sense. > > It won't let me stop the current stuck build. Would you be able to? > > From the logs it looks like it

Re: Building with Java 11

> > I'll propose merging this to master and setting up a Java 11 > build to run alongside the Java 8. That should enable folks to look at test > issues on master. +1 , I'm also willing to help with test fixes related to Java 11. El vie., 1 mar. 2019 a las 10:28, j4fm () escribió: > Ah yeah

Re: Building with Java 11

Ah yeah that makes sense. It won't let me stop the current stuck build. Would you be able to? >From the logs it looks like it succeeds up until the point it's frozen... I'm not sure what's up with it. Have you seen it freeze like this before? Maybe it's an issue with the CI agent instead?

Re: Building with Java 11

On Fri, Mar 1, 2019 at 4:14 PM j4fm wrote: > I would be happy to pull your PR and build against JDK 11 before merging. > I > can start that build now. > Bigger concern is that builds against Java 8, and is green with Java 8. I think your recent changes make that more likely to succeed

Re: Building with Java 11

I would be happy to pull your PR and build against JDK 11 before merging. I can start that build now. I see buildbot seems to have frozen. I think really my PR 419 should run before the current 409 because the former is mostly prep for the latter. If you are okay with it, I will click stop (if

Re: Building with Java 11

I've cleaned up this branch so the dependencies should now be correct (and minimal). I'm currently running a Java 8 full build with tests. Assuming that works, I'll propose merging this to master and setting up a Java 11 build to run alongside the Java 8. That should enable folks to look at test

[GitHub] jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11

jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261661356 ## File path: container/openejb-core/pom.xml ## @@ -429,6 +429,34 @@ + + javax.xml.bind +

Re: Looking for review of PR 360

I know I'm on a promise to review it - I do want to run it with a full load test against Websphere MQ, which will take a little time to set up. I'll need to dedicate a few hours to it. Thanks for the nudge though and I'll get on it as soon as I can. Jon On Fri, Mar 1, 2019 at 3:14 PM Doychin

Looking for review of PR 360

Hi guys, I did some changes on PR 360 since last someone of you looked at it. Can you check it again and see what else is needed in order to merge that? https://github.com/apache/tomee/pull/360 Thanks in advance -- Doychin Bondzhev dSoft-Bulgaria Ltd. <> smime.p7s Description: S/MIME

Re: Building with Java 11

Yeah... it'll take a few hours for those to run through. Thanks for the PRs and for keeping an eye out on the build, its much appreciated. Jon On Fri, Mar 1, 2019 at 3:00 PM j4fm wrote: > Thanks Jon. I'm keeping an eye on each run on buildbot. Maybe I should go > out for a while ;) > > > >

Re: Building with Java 11

Thanks Jon. I'm keeping an eye on each run on buildbot. Maybe I should go out for a while ;) -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

[GitHub] jgallimore edited a comment on issue #293: WIP - experimentation with Java 11

jgallimore edited a comment on issue #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#issuecomment-468682353 > (I think) PR 419 already does this as well as other related needed dependency changes. Yes, I'm wondering if this now redundant.

[GitHub] j4fm commented on a change in pull request #293: WIP - experimentation with Java 11

j4fm commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261622060 ## File path: examples/moviefun-rest/pom.xml ## @@ -171,8 +171,20 @@ org.apache.tomee -

[GitHub] jgallimore commented on issue #293: WIP - experimentation with Java 11

jgallimore commented on issue #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#issuecomment-468682353 > (I think) PR 419 already does this as well as other related needed dependency changes. Yes, I'm wondering if this now redundant. Running

[GitHub] jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11

jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261616836 ## File path: container/openejb-core/pom.xml ## @@ -429,6 +429,34 @@ + + javax.xml.bind +

[GitHub] jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11

jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261617517 ## File path: container/openejb-core/pom.xml ## @@ -429,6 +429,34 @@ + + javax.xml.bind +

[GitHub] jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11

jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261617828 ## File path: container/openejb-jee-accessors/pom.xml ## @@ -56,6 +56,16 @@ javaee-api provided

[GitHub] jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11

jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261616585 ## File path: container/openejb-core/pom.xml ## @@ -429,6 +429,34 @@ + + javax.xml.bind

[GitHub] jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11

jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261617395 ## File path: container/openejb-core/pom.xml ## @@ -429,6 +429,34 @@ + + javax.xml.bind +

[GitHub] jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11

jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261617978 ## File path: examples/moviefun-rest/pom.xml ## @@ -171,8 +171,20 @@ org.apache.tomee -

[GitHub] jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11

jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261618167 ## File path: examples/mp-rest-client/pom.xml ## @@ -52,8 +52,18 @@

[GitHub] jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11

jgallimore commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261618056 ## File path: examples/moviefun-rest/pom.xml ## @@ -171,8 +171,20 @@ org.apache.tomee -

[GitHub] otaviojava commented on a change in pull request #293: WIP - experimentation with Java 11

otaviojava commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261616154 ## File path: examples/mp-rest-client/pom.xml ## @@ -52,8 +52,18 @@

Re: Building with Java 11

418 is merged... looking at 424 now. Jon On Fri, Mar 1, 2019 at 1:53 PM j4fm wrote: > Thanks for the merges, hopefully will save time. Could I make a shameless > request for 418 too? (and 424 if poss) :D > > I'm going to keep a close eye on buildbot too, just in case. > > James > > > > -- >

Re: CXF PRs (M3)

Thanks Jon On Fri, Mar 1, 2019 at 11:03 AM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > They've both been merged - CI builds should be running. > > Jon > > On Fri, Mar 1, 2019 at 10:41 AM Gerwin Jansen > wrote: > > > +1 eagerly waiting for this! > > > > -Original Message-

[GitHub] otaviojava commented on a change in pull request #293: WIP - experimentation with Java 11

otaviojava commented on a change in pull request #293: WIP - experimentation with Java 11 URL: https://github.com/apache/tomee/pull/293#discussion_r261616154 ## File path: examples/mp-rest-client/pom.xml ## @@ -52,8 +52,18 @@

Re: CXF PRs (M3)

They've both been merged - CI builds should be running. Jon On Fri, Mar 1, 2019 at 10:41 AM Gerwin Jansen wrote: > +1 eagerly waiting for this! > > -Original Message- > From: Ivan Junckes Filho > Sent: donderdag 28 februari 2019 21:11 > To: dev@tomee.apache.org > Subject: [EXTERNAL] -

[GitHub] jgallimore merged pull request #424: TOMEE-2408 Resolve MP JWT producer always being started or duplicated

jgallimore merged pull request #424: TOMEE-2408 Resolve MP JWT producer always being started or duplicated URL: https://github.com/apache/tomee/pull/424 This is an automated message from the Apache Git Service. To respond

[GitHub] jgallimore merged pull request #418: Bump geronimo openapi & safeguard to released versions

jgallimore merged pull request #418: Bump geronimo openapi & safeguard to released versions URL: https://github.com/apache/tomee/pull/418 This is an automated message from the Apache Git Service. To respond to the message,

Re: Building with Java 11

Thanks for the merges, hopefully will save time. Could I make a shameless request for 418 too? (and 424 if poss) :D I'm going to keep a close eye on buildbot too, just in case. James -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Building with Java 11

I've merged those 2 PRs in. Let's see what the actual diff is for my branch now. Jon On Fri, Mar 1, 2019 at 1:28 PM Otávio Gonçalves de Santana < osant...@tomitribe.com> wrote: > Hey JonG, > What do you think if you move this branch to the TomEE project? > > On Wed, Jan 9, 2019 at 10:40 AM

[GitHub] jgallimore merged pull request #419: TOMEE-2274 (JAXB bump); exclusions for CXF 3.3.0; fix those existing build WARNINGs

jgallimore merged pull request #419: TOMEE-2274 (JAXB bump); exclusions for CXF 3.3.0; fix those existing build WARNINGs URL: https://github.com/apache/tomee/pull/419 This is an automated message from the Apache Git

[GitHub] jgallimore merged pull request #416: TOMEE-2408 Remove dependency on MP JAR filenames

jgallimore merged pull request #416: TOMEE-2408 Remove dependency on MP JAR filenames URL: https://github.com/apache/tomee/pull/416 This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] jgallimore merged pull request #409: TomEE-2472 updating mp rest client and cxf

jgallimore merged pull request #409: TomEE-2472 updating mp rest client and cxf URL: https://github.com/apache/tomee/pull/409 This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: Building with Java 11

Hey JonG, What do you think if you move this branch to the TomEE project? On Wed, Jan 9, 2019 at 10:40 AM Jean-Louis Monteiro < jlmonte...@tomitribe.com> wrote: > Great job Jon. > I did some tests so, so we should be able to get something green hopefully > soon > -- > Jean-Louis Monteiro >

Re: Building with Java 11

For PR 419 and 409 all the full tests pass too. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Building with Java 11

I already updated all the JAXB related artifacts to 2.3.1 which comes with CXF 3.3.0 too. I already added all the transitive dependency exclusions. Your extra ones could just be added on top of that. The work is in PR 419 which was already reviewed and approved. It would be great to have that

Re: Building with Java 11

Hi Jon, could not we move your branch to apache/tomee repository? What you guys think about it? Em qua, 9 de jan de 2019 às 09:40, Jean-Louis Monteiro < jlmonte...@tomitribe.com> escreveu: > Great job Jon. > I did some tests so, so we should be able to get something green hopefully > soon > --

RE: CXF PRs (M3)

+1 eagerly waiting for this! -Original Message- From: Ivan Junckes Filho Sent: donderdag 28 februari 2019 21:11 To: dev@tomee.apache.org Subject: [EXTERNAL] - CXF PRs (M3) Hey guys, it seems these PRs are already reviewed. Can someone merge them? It would be very nice if this makes to

Re: MicroProfile Integration in Plus and Plume

Hi Roberto, PR 418 is also ready now that openapi and safeguard latest release versions are in maven -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

[GitHub] j4fm commented on issue #418: Bump geronimo openapi & safeguard to released versions

j4fm commented on issue #418: Bump geronimo openapi & safeguard to released versions URL: https://github.com/apache/tomee/pull/418#issuecomment-468601047 These are now in maven. So ready to go This is an automated message