Hi Mark, I believe that Qpid Team members requested an access to TCK earlier in order to test compatibility of Qpid JMS clients with JMS specs. We added maven module  to run TCK tests against Qpid Broker-J. Though, TCK is not part of Qprid Broker-J project and it has to be provided externally. The TCK bundles need to be downloaded separately and the path to the TCK folder needs to be specified to the maven build as JVM property. Both TCK tests for JMS 1.1 and JMS 2.0 can be run. However, currently, only older Oracle proprietary TCKs are supported due to hard-coded paths to the dependency jars.
In order to run TCK tests with new Jakarta EE bundle, the maven profile settings needs to be amended. I will change that later. So, in general, I would like to continue running TCK tests with Qpid JMS clients and Qpid Broker-J using Jakarta EE bundle. If Jakarta EE compatible logo is required to add to Qpid Project, I suppose, we can add it. Mark, Do you know whether there are any plans to release TCK bundles into maven repository? I suppose that JMS 1.1 TCK is not supported by Jakarta EE and if I still want to run JMS 1.1 TCK I need to use Oracle provided bundle. Kind Regards, Alex  https://cwiki.apache.org/confluence/display/qpid/How+To+Build+Qpid+Broker-J#HowToBuildQpidBroker-J-JMSTCK On Sun, 17 Feb 2019 at 19:01, Mark Thomas <ma...@apache.org> wrote: > Ping. > > Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet. > > Mark > > PS If you don't want to build from source, there are nightly TCK builds > available here: > https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/ > > > On 21/01/2019 10:46, Mark Thomas wrote: > > Apologies for the noise. > > > > The correct link for  is: > > > > https://jakarta.ee/legal/trademark_guidelines/ > > > > I've also corrected a handful of the project BCCs. > > > > Mark > > > > > > On 18/01/2019 22:53, Mark Thomas wrote: > >> Hi all, > >> > >> I am writing to your dev@ lists (on BCC) as your project has, in the > >> past, requested access to the Java EE TCKs while they were controlled by > >> Sun and then Oracle. > >> > >> As I am sure you are aware, Java EE has moved to Eclipse and is now > >> Jakarta EE. The good news is that the TCKs have been open sourced. > >> > >> https://github.com/eclipse-ee4j/jakartaee-tck > >> > >> (I haven't tried to build the latest TCK from source yet but it is on my > >> TODO list.) > >> > >> Shipping compatible implementations of the Jakarta EE specs (and being > >> able to make public statements to that effect) will be subject only to > >> the spec  and TCK  licenses. There will no longer be a TCK > >> agreement or NDA to sign. However... > >> > >> The question has arisen whether or not any ASF projects will want to use > >> the Jakarta EE compatible logo . If a project wants to be able to do > >> this, there are some organisational hoops to jump through. Before the > >> ASF starts down that path the board has asked me to see if there are any > >> projects that want to use the Jakarta EE compatible logo. After all, > >> there is no point jumping through the hoops if no-one wants to use the > logo. > >> > >> With the above in mind can you please discuss this amongst your project > >> community and reply back to jcp-o...@apache.org whether or not your > >> project is interested in being able to use the Jakarta EE compatible > >> logo. I ask that you complete this no later than the next board meeting > >> (20th February 2019). > >> > >> If you have any questions about any of the above, please also use > >> jcp-o...@apache.org to ask them. > >> > >> Thanks, > >> > >> Mark > >> > >> > >>  https://www.eclipse.org/legal/efsl.php > >>  https://www.eclipse.org/legal/tck.php > >>  https://www.eclipse.org/legal/tck.php > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > >