Hi Benoit, The OFBiz community is in the process of migrating from derby to H2 for their product(s) regarding development and demo purposes. I expect the James community could do something similar.
Met vriendelijke groet, Pierre Smits On Fri, Dec 5, 2025 at 2:14 PM [email protected] <[email protected]> wrote: > Hello all, > > I learned yesterday that Apache Derby, that is the default driver ued by > the JPA application, is now retired. > > As such I propose to instead use H2, also an Apache project, as an > (almost) drop in replacement. > > > CF > - https://issues.apache.org/jira/browse/JAMES-4155 > - https://github.com/apache/james-project/pull/2875 > > Here are some remarks: > > > - The change do not impact exising instalations, which can still > continue using retired Apache Derby > - It only prevent new Derby install to occurs > - We still encourage users from migrating to H2 > - Both DBs being SQL, data can likely be exportd from Derby and > importd into H2. > > Best regards, > > Benoit TELLIER > > > -------- Forwarded Message -------- > Subject: Apache Derby is now retired > Date: Wed, 3 Dec 2025 09:38:15 -0800 > From: Richard Hillegas <[email protected]> > Reply-To: [email protected] > To: [email protected] > > > > The DB PMC announces the retirement of its Derby sub-project, due to > prolonged low activity. Derby is a small-footprint, pure-Java relational > database. Derby runs embedded in a local application as well as > client-server over a network. Databases can live on disk or in memory. > Existing, official versions support JVMs from Java 1.3 up through Java > 21. The development mainline builds and tests cleanly on Java 25. > > The project's resources remain available in a read-only state. This > includes the website (https://db.apache.org/derby/), mailing lists, wiki > (https://cwiki.apache.org/confluence/display/DERBY/FrontPage), > Subversion repository, and JIRA bug tracker. Official distributions > remain available on an as-is basis at > https://db.apache.org/derby/derby_downloads.html. > >
