Re: DISCUSS geronimo-security_1.0_spec content unclear

> On Sep 4, 2019, at 2:10 AM, Romain Manni-Bucau wrote: > > No I guess it was right, "that are" ;) = fork @G only when we need to > change some impl/default provider. Right. A few things in my mind at least: - Industry health: we (Apache) are the only other implementations of Activation,

Re: DISCUSS geronimo-security_1.0_spec content unclear

> On Sep 4, 2019, at 6:04 AM, Mark Struberg wrote: > > No, this is an intended situation. > When one fully passes the TCK then you get the EFSL. This 'removes' the > copyleft nature of the EPL. > The details are quite nested in the legal papers, but that's it basically. > > If we just upgrade

Re: DISCUSS geronimo-security_1.0_spec content unclear

We cant, only impl+api are certified so no issue ;) Le mer. 4 sept. 2019 à 17:01, Jean-Louis Monteiro a écrit : > I'd like to certify some of them if possible of course. > > Le mer. 4 sept. 2019 à 15:33, Romain Manni-Bucau > a écrit : > >> Not sure I'm following Mark, EPL is fine for us ( >>

Re: JTA JMS Spec question, connection leakage

Nice work! So one final grievance. This has to do with MDBs... we see this message spammed to sysout all the time when an MDB consumes a message: Sep 04, 2019 9:41:37 AM org.apache.geronimo.connector.work.WorkerContext run INFO: Removing non-required WorkContextHandler with no context:

Re: JTA JMS Spec question, connection leakage

Yep, should be on 7.0.x, 7.1.x and master. Jon On Wed, Sep 4, 2019 at 3:35 PM Jonathan S. Fisher wrote: > Nice, thanks for cleaning that merge up. This got ported to both 7.1.x and > master? > > > > On Wed, Sep 4, 2019 at 8:10 AM Jonathan Gallimore < > jonathan.gallim...@gmail.com> wrote: > >

Re: JTA JMS Spec question, connection leakage

Nice, thanks for cleaning that merge up. This got ported to both 7.1.x and master? On Wed, Sep 4, 2019 at 8:10 AM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > Ok, think I found it. The code in AutoConnectionTracker.handleObtained() > changed ever so slightly, but the effect was

Re: DISCUSS geronimo-security_1.0_spec content unclear

Not sure I'm following Mark, EPL is fine for us ( https://www.apache.org/legal/resolved.html) and G spec jars are not officially certified so don't change of license anytime. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: JTA JMS Spec question, connection leakage

Ok, think I found it. The code in AutoConnectionTracker.handleObtained() changed ever so slightly, but the effect was proxyConnection() didn't get called. I've fixed that, and the test passes. I've also run the JMS Arquillian tests which work ok too. Cheers! Jon On Wed, Sep 4, 2019 at 12:16 PM

Re: DISCUSS geronimo-security_1.0_spec content unclear

No, before that it was CDDL+GPL. It just moved to EPL, which is also CatB LieGrue, strub > Am 04.09.2019 um 15:06 schrieb Romain Manni-Bucau : > > @Mark: didn't change with jakarta donation? can you open a ticket on > jakartee tracker please? > > Romain Manni-Bucau > @rmannibucau

Re: DISCUSS geronimo-security_1.0_spec content unclear

@Mark: didn't change with jakarta donation? can you open a ticket on jakartee tracker please? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github |

Re: DISCUSS geronimo-security_1.0_spec content unclear

No, this is an intended situation. When one fully passes the TCK then you get the EFSL. This 'removes' the copyleft nature of the EPL. The details are quite nested in the legal papers, but that's it basically. If we just upgrade our existing API to be binary compat then we have no IP issues.

Re: JTA JMS Spec question, connection leakage

Thanks Jonathan! I merged this in, and ported to 7.1.x. I've run into a test failure with org.apache.openejb.resource.GeronimoConnectionManagerFactoryTest. No idea what the root cause is yet - checking it out. I haven't pushed this to master yet (will try and resolve that test issue first).

[GitHub] [tomee] asfgit merged pull request #547: Add jgallimore's JMS Tests and fix TomEE-2506 autoconnection tracker warning

asfgit merged pull request #547: Add jgallimore's JMS Tests and fix TomEE-2506 autoconnection tracker warning URL: https://github.com/apache/tomee/pull/547 This is an automated message from the Apache Git Service. To

[GitHub] [tomee] jgallimore commented on issue #547: Add jgallimore's JMS Tests and fix TomEE-2506 autoconnection tracker warning

jgallimore commented on issue #547: Add jgallimore's JMS Tests and fix TomEE-2506 autoconnection tracker warning URL: https://github.com/apache/tomee/pull/547#issuecomment-527829227 There's a few conflict on here, but it looks good. I'll get it merged.

Re: Java EE 8 versions of APIs

Security and annotations are up for vote. I have JavaMail 1.6 created and almost ready for VOTE. We don't have standalone TCK to run for those, but when they are released, I'll get them all integrated and I'll push a TCK build on TomEE so we have a view on what we need to fix. -- Jean-Louis

Re: DISCUSS geronimo-security_1.0_spec content unclear

exactly. Main ambiguity is for API using a provider as only impl dependency like jsonp/jsonb ( https://github.com/apache/geronimo-specs/blob/trunk/geronimo-jsonb_1.0_spec/src/main/java/javax/json/bind/spi/JsonbProvider.java#L30 ). Think it makes sense to keep it hosted to change this value even if

Re: DISCUSS geronimo-security_1.0_spec content unclear

so for instance activation and javamail would stay in Geronimo Specs and let's say @Inject would be Eclipse? -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, Sep 4, 2019 at 11:11 AM Romain Manni-Bucau wrote: > No I guess it was right, "that are" ;) =

Re: DISCUSS geronimo-security_1.0_spec content unclear

No I guess it was right, "that are" ;) = fork @G only when we need to change some impl/default provider. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: DISCUSS geronimo-security_1.0_spec content unclear

> This is my current thinking as well; maintain apis that are impls, use the EPL version otherwise. I believe you meant "that are not impls ..." I'll make the changes on the javaee-api jar -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Sep 3, 2019 at