Yep, I would say much the same. I'd avoid testcontainers for the initial/default testing for similar reasons whenever there are clear reasonable and faster alternatives, and in this case there seems likely to be multiple. I'd use it (/docker/podman) for more secondary checking interaction with e.g specific DB impls that dont otherwise fit that core model.
On Thu, 25 Sept 2025 at 07:29, Francois Papon <[email protected]> wrote: > > Hi, > > For using both testcontainer and H2 I would prefer to use H2 if possible > because testcontainer can slow down the build/test and it's not always > available on CI runners because as runners can be a docker, running a > docker in a docker can be blocked for security reason. > > regards, > > François > [email protected] > [email protected] > > Le 25/09/2025 à 06:54, Jean-Baptiste Onofré a écrit : > > Hi > > > > Thanks for your message Clebert. > > > > We are not in the rush but worth to explore the alternatives. > > > > I think we have two options (for both Artemis and Classic): > > 1. Find another file db like h2 > > 2. Use test containers > > > > My preference is for 2 as the tests should be more accurate using a “real” > > database. > > > > But again, we have time to prepare this change: even if the project is > > retired, the artifacts are still there (it means that we won’t have new > > versions and maintenance but it gives us time). > > > > Regards > > JB > > > > Le mer. 24 sept. 2025 à 21:03, Clebert Suconic <[email protected]> > > a écrit : > > > >> I saw a discussion today about Derby retiring... > >> > >> We still use it as part of our testsuites, both on ActiveMQ "Classic" > >> and "Artemis"... > >> > >> > >> I wonder what should we do about this? Should we let it retire, should > >> we still use it as read-only (as its a good tool for testing), or > >> should we ask them to keep it alive? > >> > >> > >> If we let it retire, what would we replace it with? > >> > >> -- > >> Clebert Suconic > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> For further information, visit: https://activemq.apache.org/contact > >> > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
