If you want, I can share a Gradle project which runs the 3.1 Jakarta JMS TCK tests with Artemis. Without looking at the script I recall that
- downloading of the TCK, compiling the TCK, and configuring the TCK is done as Gradle tasks - use of Gradle is justified by the fact that Gradle is able to download client dependencies from maven repository (including it's transitive dependencies) and provide a class path for TCK tests to use so client is on it - the only broker-specific part is creating queues and topics on the broker, otherwise it is not broker specific - there isn't really any secret to it, just compile tests with run, patch the config file with connection factory name and the classpath, and start tests On Wed, Jul 12, 2023, 18:32 Justin Bertram <jbert...@apache.org> wrote: > Would the contents of that repository (assuming a TCK is set up there) not > be out of date at this point? It seems like we could just grab the relevant > TCK [1] from Eclipse and create a new repo with it. What's the benefit of > inspecting or using the old repo? > > > Justin > > [1] https://download.eclipse.org/ee4j/jakartaee-tck/ > > On Wed, Jul 12, 2023 at 8:47 AM David Blevins <david.blev...@gmail.com> > wrote: > > > Hey All, > > > > Matt and I were talking on the Jakarta lists about getting the Jakarta > > Messaging TCK setup for ActiveMQ Classic. > > > > I know there was a TCK setup at some point as I’ve sat next to Hiram > while > > he ran it way back in the day. I don’t recall if he was running the > > Geronimo TCK setup, however, or if he had managed to get a setup with > just > > plain ActiveMQ. > > > > If there was a TCK setup, it would probably be here: > > > > - svn list https://svn.apache.org/repos/tck/activemq-tck > > > > Even if you are a committer, you would not have access unless you were > > around in the 2004-2010 timeframe and agreed to be confidential with the > > TCK materials and results. > > > > If there are any folks around from back then, can you quickly check to > see > > if something is there? > > > > If so, we will now be able to safely make that repo public and convert it > > to git. > > > > > > -David > > > > >
