I dont have access to the old area either.

I also think that given the likely age of it, I wouldn't really be
bothered about whatever might be in there. Starting with the more
recent Jakarta Messaging TCK public download should not be hard. The
Jakarta Messaging TCK is linked from
https://jakarta.ee/specifications/messaging/3.1/ (or earlier
versions).

I'd guess there is still an amount of work to do before 5.x could pass
the Jakarta Messaging TCK though given it doesnt do various JMS 2.0
additions yet like shared subs, async send, delivery delay, receive
body...though perhaps addressing that is why Matt is looking to set it
up now.

On Wed, 12 Jul 2023 at 17:24, 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
> >
> >

Reply via email to