Fwd: [apache/db-jdo] JDO-827 Simplify JNDI (PR #81)

[Craig Russell]

There are over half a dozen messages regarding JDO-827/PR#81.

Is there a problem with the asf.yaml configuration that prevents these from 
being threaded?

I know we updated asf.yaml recently but somehow this does not meet my 
expectations.

Thanks,
Craig

> Begin forwarded message:
> 
> From: Tilmann 
> Subject: Re: [apache/db-jdo] JDO-827 Simplify JNDI (PR #81)
> Date: July 6, 2023 at 11:43:49 PDT
> To: apache/db-jdo 
> Cc: Subscribed 
> Reply-To: apache/db-jdo 
> 
> 
> 
> Merged #81  into main.
> 
> —
> Reply to this email directly, view it on GitHub 
> , or unsubscribe 
> .
> You are receiving this because you are subscribed to this thread.
> 

Craig L Russell
c...@apache.org

[jira] [Created] (JDO-832) Remove RunTCK option jdo.tck.skipJndi

[Michael Bouschen (Jira)]

Michael Bouschen created JDO-832:


 Summary: Remove RunTCK option jdo.tck.skipJndi
 Key: JDO-832
 URL: https://issues.apache.org/jira/browse/JDO-832
 Project: JDO
  Issue Type: Task
  Components: tck
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen
Assignee: Michael Bouschen
 Fix For: JDO 3.2.2, JDO 3.3


With JDO-827 the TCK comes with its own JNDI mock implementation.

Without an JNDI implemention we needed to skip the JNDI TCK test cases when 
running the tck from an automatic build. This is not necessary anymore, so we 
do not need the  option jdo.tck.skipJndi anymore.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)