This is an automated email from the ASF dual-hosted git repository.

jungm pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomee-site-generator.git


The following commit(s) were added to refs/heads/main by this push:
     new fcdf0e3  tomee 10.3.0 and 11.0.0-M2 released
fcdf0e3 is described below

commit fcdf0e3268825e721f754f8ecf886e4e96f460fd
Author: Markus Jung <[email protected]>
AuthorDate: Tue Nov 10 14:57:59 2026 +0100

    tomee 10.3.0 and 11.0.0-M2 released
---
 .../org/apache/tomee/website/Configuration.java    |   4 +-
 src/main/jbake/content/10.3.0/migration-guide.adoc | 384 +++++++++++++++++++
 src/main/jbake/content/10.3.0/release-notes.adoc   | 179 +++++++++
 .../jbake/content/11.0.0-M2/migration-guide.adoc   | 422 +++++++++++++++++++++
 .../jbake/content/11.0.0-M2/release-notes.adoc     | 218 +++++++++++
 src/main/jbake/content/download-archive.adoc       |  30 +-
 src/main/jbake/content/download.adoc               |  44 ++-
 src/main/jbake/templates/index.gsp                 |   6 +-
 src/main/resources/ignored.txt                     |   2 +-
 9 files changed, 1261 insertions(+), 28 deletions(-)

diff --git a/src/main/java/org/apache/tomee/website/Configuration.java 
b/src/main/java/org/apache/tomee/website/Configuration.java
index f640b56..676c844 100644
--- a/src/main/java/org/apache/tomee/website/Configuration.java
+++ b/src/main/java/org/apache/tomee/website/Configuration.java
@@ -242,9 +242,9 @@ public class Configuration {
 //        if (1 == 1) return new Source[0]; // uncomment this line to generate 
only the main site pages.
         return new Source[]{
                 // TOMEE NEXT
-                new Source("https://github.com/apache/tomee.git";, 
"tomee-project-11.0.0-M1", "tomee-11.0", 
true).related(microProfile71).related(jakartaEE11).javadoc("^org.apache.(openejb|tomee).*"),
+                new Source("https://github.com/apache/tomee.git";, 
"tomee-project-11.0.0-M2", "tomee-11.0", 
true).related(microProfile71).related(jakartaEE11).javadoc("^org.apache.(openejb|tomee).*"),
                 // TOMEE CURRENT
-                new Source("https://github.com/apache/tomee.git";, 
"tomee-10.x", "tomee-10.2", 
false).related(microProfile61).related(jakartaEE10).javadoc("^org.apache.(openejb|tomee).*"),
+                new Source("https://github.com/apache/tomee.git";, 
"tomee-10.x", "tomee-10.3", 
false).related(microProfile61).related(jakartaEE10).javadoc("^org.apache.(openejb|tomee).*"),
             //    new Source("https://github.com/apache/tomee.git";, 
"tomee-9.x", "tomee-9.0", 
false).related(microProfile5).related(jakartaEE9).javadoc("^org.apache.(openejb|tomee).*"),
            //     new Source("https://github.com/apache/tomee.git";, 
"tomee-8.x", "tomee-8.0", 
false).related(microProfile2).related(jakartaEE8).javadoc("^org.apache.(openejb|tomee).*"),
             //    new Source("https://github.com/apache/tomee.git";, 
"tomee-7.1.x", "tomee-7.1", false).javadoc("^org.apache.(openejb|tomee).*"),
diff --git a/src/main/jbake/content/10.3.0/migration-guide.adoc 
b/src/main/jbake/content/10.3.0/migration-guide.adoc
new file mode 100644
index 0000000..acdf72c
--- /dev/null
+++ b/src/main/jbake/content/10.3.0/migration-guide.adoc
@@ -0,0 +1,384 @@
+= Migrating to Apache TomEE 10.3.0
+:index-group: Release Notes
+:jbake-type: page
+:jbake-status: published
+:toc:
+
+TomEE 10.3.0 contains a large number of security hardening changes. Many of 
them tighten defaults that earlier TomEE
+versions left open, so applications and deployments that relied on the old 
behavior need to be adjusted. This guide
+lists every change that can affect an upgrade from TomEE 10.2.x, explains who 
is affected, and shows what to change.
+Where TomEE offers a switch to restore the previous behavior, it is listed as 
well. Use these switches only as a
+temporary measure: they re-open the issue the change fixed.
+
+See the link:release-notes.html[release notes] for the full list of changes.
+
+System properties mentioned in this guide can be set in 
`conf/system.properties` or passed as `-D` options to the JVM,
+unless the section says otherwise.
+
+== Removed Modules
+
+The following modules are no longer built or published. None of them was part 
of a TomEE distribution by default.
+
+[cols="1,2,2",options="header"]
+|===
+|Module|What it provided|Replacement
+|`openejb-hessian` 
(link:https://issues.apache.org/jira/browse/TOMEE-4700[TOMEE-4700])
+|The `hessian` server service exposing `@Remote` EJBs over Hessian, 
`HessianInitialContextFactory` and the CDI `@Hessian` client injection
+|EJBd (`ejbd`/`ejbds`, or EJBd over HTTP at `/tomee/ejb`), JAX-RS or JAX-WS
+|`openejb-ssh` 
(link:https://issues.apache.org/jira/browse/TOMEE-4701[TOMEE-4701])
+|The `ssh` service (port 4222), a JAAS-authenticated administration shell
+|JMX, `tomee-maven-plugin` or remote deployment through the Deployer, the 
`bin/openejb` and `bin/tomee` commands
+|`openejb-common-cli` 
(link:https://issues.apache.org/jira/browse/TOMEE-4702[TOMEE-4702])
+|The command framework behind the SSH shell
+|None needed. The `bin/openejb` commands (`start`, `stop`, `deploy`, `cipher`, 
...) are not affected.
+|`openejb-http` 
(link:https://issues.apache.org/jira/browse/TOMEE-4707[TOMEE-4707])
+|The standalone HTTP server (`httpejbd` service, port 4204) used by OpenEJB 
standalone and embedded containers, including its Jetty backend and the 
embedded JAX-RS/JAX-WS registries
+|TomEE, TomEE embedded or the Arquillian TomEE adapters. EJBd over HTTP is 
available in TomEE at `/tomee/ejb` with `tomee.remote.support=true`.
+|===
+
+Removing `openejb-http` has these further consequences:
+
+* OpenEJB standalone, `ApplicationComposer`, `EJBContainer` and 
`arquillian-openejb-embedded` no longer serve JAX-RS or
+  JAX-WS endpoints over HTTP. The `conf/httpejbd.properties` file, the 
`httpejbd.*` properties and the
+  `--httpejbd-bind`/`--httpejbd-port` options are gone.
+* `@EnableServices` no longer has the `jaxrs`, `jaxws` and `httpDebug` 
attributes, and `@JaxrsProviders` no longer has
+  `applicationName`. Tests that used them need to move to TomEE embedded or 
Arquillian.
+* The `org.apache.openejb.server.httpd.ServerServlet` class is now 
`org.apache.tomee.catalina.remote.ServerServlet`.
+  If your `web.xml` declares this servlet to expose EJBd over HTTP, update the 
class name. `EEFilter`,
+  `BeginWebBeansListener` and `EndWebBeansListener` moved to the 
`org.apache.tomee.catalina` package as well.
+* The default of `openejb.rest.wildcard` changed from `.*` to `*`.
+
+== Build Tools
+
+=== Maven 3.10.0 or newer
+
+The TomEE Maven plugins no longer use the Maven 2 API
+(link:https://issues.apache.org/jira/browse/TOMEE-4705[TOMEE-4705]). 
`tomee-maven-plugin` and the other TomEE Maven
+plugins now require Maven 3.10.0 or newer and Java 17. Plugin coordinates, 
goals and parameters are unchanged.
+
+=== Gradle plugin
+
+The Gradle plugin is built against the current Gradle API
+(link:https://issues.apache.org/jira/browse/TOMEE-4706[TOMEE-4706]) and works 
with Gradle 8.x and 9.x. The plugin id
+`org.apache.tomee.tomee-embedded` and its DSL are unchanged.
+
+=== quickSession defaults to false
+
+The `quickSession` option makes the dev tooling generate session ids with a 
non-secure random generator. It now
+defaults to `false` in:
+
+* `tomee-maven-plugin` (`quickSession`, user property 
`tomee-plugin.quick-session`)
+* `tomee-embedded-maven-plugin` (user property 
`tomee-embedded-plugin.quickSession`)
+* TomEE embedded (`Configuration.quickSession`)
+* the Gradle `tomee-embedded` task (`quickSession`)
+
+Startup can be slightly slower on systems with little entropy. Set the option 
to `true` to restore the previous behavior.
+
+=== LiveReload only listens on localhost
+
+The LiveReload connector of `tomee-embedded-maven-plugin` (port 35729) now 
binds to `localhost` and rejects WebSocket
+handshakes whose `Origin` is not a loopback address. Browser extensions and 
requests without an `Origin` are still
+accepted. If you use LiveReload from another machine, a VM or a container 
host, configure:
+
+[source,xml]
+----
+<liveReload>
+  <host>0.0.0.0</host>
+  <allowAnyOrigin>true</allowAnyOrigin>
+</liveReload>
+----
+
+=== Credentials over plain HTTP
+
+The `tomee-maven-plugin` command goals (`deploy`, `undeploy`, ...) log a 
warning when they send a user and password to a
+non-local host over plain HTTP. Configure an HTTPS port with 
`tomee-plugin.https` and set
+`tomee-plugin.command-force-https=true` to send credentials over HTTPS.
+
+== MicroProfile JWT
+
+=== The MP-JWT filter requires authMethod "MP-JWT"
+
+Before, any class annotated with `@LoginConfig` enabled MP-JWT processing, 
whatever its `authMethod`. Now JWT
+processing is only enabled for:
+
+[source,java]
+----
+@LoginConfig(authMethod = "MP-JWT")
+----
+
+Applications that use a different `authMethod` (for example `BASIC`) and still 
expect bearer tokens to be accepted must
+change it to `MP-JWT`.
+
+=== Role constraints are resolved per resource class
+
+`@RolesAllowed`, `@PermitAll` and `@DenyAll` are now resolved for each 
resource class separately:
+
+* A method inherited by several resource classes no longer gets the union of 
the roles of all these classes. Each class
+  gets the roles declared for it.
+* An empty `@RolesAllowed({})` denies all callers (HTTP 403). Before, it 
allowed everyone. Use `@PermitAll` if the
+  method should be public.
+* An unannotated subclass inherits the class-level annotation of an annotated 
superclass for the methods it inherits
+  (link:https://issues.apache.org/jira/browse/TOMEE-4730[TOMEE-4730]). Such 
endpoints were unprotected before and now
+  return 401 or 403 for callers without the required role. A class carrying 
more than one of these annotations fails
+  the deployment.
+
+Review resources that use inheritance or empty role lists.
+
+=== Negative clock skew is rejected
+
+A negative `mp.jwt.verify.clock.skew` used to disable the expiry check of 
tokens. It now fails the deployment with a
+`DeploymentException`. Set the value to `0` or a positive number of seconds.
+
+== Authentication and Identity Stores
+
+=== LDAP identity store
+
+* Caller names are escaped (RFC 4515) when TomEE builds search filters, and 
DNs built from `callerBaseDn` are escaped
+  as well. If your application escaped caller names itself, remove that code, 
since names would now be escaped twice.
+  Caller names containing `*`, `(`, `)` or `\` no longer act as wildcards or 
filter syntax.
+* A caller with an empty or missing password is rejected without a bind 
attempt. Before, an LDAP server allowing
+  anonymous binds accepted such logins.
+
+=== Login modules
+
+* `SQLLoginModule` rejects users whose stored password is `NULL`. Before, such 
users could log in without a password.
+  Give these users a password or remove them.
+* `PropertiesLoginModule` reports `Username or password does not match` for 
both an unknown user and a wrong password.
+  Update anything that parses the old messages.
+
+=== PBKDF2 password hashes
+
+`TomEEPbkdf2PasswordHash` now only accepts the algorithms 
`PBKDF2WithHmacSHA1`, `PBKDF2WithHmacSHA224`,
+`PBKDF2WithHmacSHA256`, `PBKDF2WithHmacSHA384` and `PBKDF2WithHmacSHA512` with 
at least 1024 iterations, both for new
+hashes and for stored hashes:
+
+* Logins whose stored hash uses fewer iterations or another algorithm fail, 
and TomEE logs a warning once.
+* `Pbkdf2PasswordHash.Algorithm` or `Pbkdf2PasswordHash.Iterations` parameters 
outside these limits make the
+  initialization fail with an `IllegalArgumentException`.
+* Malformed stored hashes fail the login instead of throwing an exception.
+
+Rehash affected passwords with stronger parameters. As a temporary measure, 
set the system property
+`tomee.security.pbkdf2.allow-weak-parameters=true` to accept weak stored 
hashes. TomEE then logs a warning for each
+weak parameter combination it accepts.
+
+=== Tomcat user identity store
+
+The identity store behind `@TomcatUserIdentityStoreDefinition` now checks 
passwords with the `CredentialHandler` of the
+`UserDatabaseRealm` in `conf/server.xml` that uses the same user database 
resource:
+
+* Passwords stored as digests in `tomcat-users.xml` are verified against the 
password the user enters. Sending the
+  stored digest itself no longer works.
+* A wrong password results in `INVALID` instead of `NOT_VALIDATED`.
+* If no matching realm is found, TomEE compares passwords as plain text and 
logs a warning.
+
+Make sure the `CredentialHandler` of the realm matches the format of the 
passwords in `tomcat-users.xml`.
+
+=== Principal names are no longer mapped to roles
+
+A user authenticated by a Tomcat realm was implicitly given a role with the 
same name as the user (for example user
+`admin` got role `admin`). This no longer happens: roles come only from the 
realm. Group principals are still mapped
+by name. If your application relied on this, assign the role to the user in 
the realm.
+
+=== Static3DES password cipher
+
+Using the `Static3DES` password cipher for resource passwords logs a warning: 
it uses a key shipped with TomEE and
+only obfuscates the password. Nothing breaks, but consider a custom 
`PasswordCipher` or a `cdi:` cipher.
+
+== Authorization
+
+=== EJB method permissions are enforced on Java 21 and newer
+
+On Java 21 and newer, TomEE 10.2.0 skipped the JACC check for EJB method 
permissions and logged
+`Skipping JACC authorization checks as TomEE running on JDK 21+`. All callers 
could invoke EJBs regardless of
+`@RolesAllowed` and `@DenyAll`. TomEE 10.3.0 evaluates these permissions 
through the installed policy on all JDKs.
+
+If you run on Java 21 or newer, callers without the required role now get an 
`EJBAccessException`. Check the role
+assignments of your users and the `@RolesAllowed` annotations of your EJBs. If 
no JACC policy is installed, EJB access
+is denied.
+
+=== Internal EJBs require an admin role
+
+Internal EJBs such as the Deployer (`openejb/DeployerBusinessRemote`) and 
`ConfigurationInfo` always require the
+`tomee-admin` or `openejb-admin` role. Before, the check was skipped in the 
default `development` profile. TomEE also
+no longer creates a `tomee`/`tomee` user with the `tomee-admin` role when 
`tomcat-users.xml` is empty.
+
+Remote deployment, for example with the `tomee-maven-plugin` deploy goals, now 
needs a user with one of these roles in
+`conf/tomcat-users.xml`:
+
+[source,xml]
+----
+<role rolename="tomee-admin"/>
+<user username="deployer" password="..." roles="tomee-admin"/>
+----
+
+The Arquillian remote adapter, `RemoteTomEEEJBContainer` and 
`tomee-maven-plugin` with `reloadOnUpdate` disable the
+check themselves for the servers they start. To disable it for a server, set
+`openejb.internal.beans.security.enabled=false`.
+
+== Web Services, JAX-RS and Routing
+
+=== JAX-WS endpoints protect all HTTP methods
+
+The security constraint TomEE generates for EJB web services with an 
`auth-method` used to cover only `GET` and `POST`.
+It now covers all HTTP methods and denies uncovered methods. `PUT`, `DELETE`, 
`OPTIONS` and other methods now require
+authentication as well. There is no switch to restore the old behavior.
+
+=== EJB web services in a WAR enforce their auth-method
+
+EJB web services packaged in a WAR were published without applying the 
`<web-service-security>` settings
+(`auth-method`, `transport-guarantee`, `realm-name`) from `openejb-jar.xml`. 
They are now enforced:
+
+* Unauthenticated calls, including `?wsdl` requests, get HTTP 401.
+* An `auth-method` other than `BASIC`, `DIGEST`, `CLIENT-CERT` or `NONE` fails 
the deployment.
+* If the webapp has its own `login-config` with a different method, the webapp 
setting wins and TomEE logs a warning.
+
+Set `<auth-method>NONE</auth-method>` (or remove it) for endpoints that are 
meant to be public. Role names are still
+configured with `tomee.jaxws.security-role.<context name>`.
+
+=== JAX-RS responses for EJBException
+
+When an `EJBException` has no mapper of its own, the default JAX-RS mapper 
used to return the exception message as a
+`text/plain` body. It now returns an empty HTTP 500 response and logs the 
message on the server. Exceptions whose cause
+has a mapper are not affected.
+
+If clients parse the error body, register your own `ExceptionMapper`. As a 
temporary measure, set
+`openejb.jaxrs.ejb-exception-mapper.expose-message=true` to restore the old 
body.
+
+=== RouterValve forwards
+
+Forward routes in `WEB-INF/tomee-router.conf` are normalized and checked 
before forwarding:
+
+* Targets that are not absolute paths, cannot be decoded or point into 
`WEB-INF` or `META-INF` get HTTP 404.
+* Targets protected by a security constraint the caller does not satisfy get 
HTTP 403. Before, the forward bypassed
+  the constraint.
+
+Redirect routes are not affected.
+
+== Remote EJB and Server Services
+
+=== Remote DataSource lookup is disabled
+
+Remote clients could look up a DataSource over EJBd and receive its connection 
details, including database
+credentials. This is now refused with a `NamingException` (`Remote DataSource 
lookup is disabled`), for `ejbd`, `ejbds`
+and EJBd over HTTP. Remote EJB calls are not affected.
+
+Clients should not connect to the database with server credentials. If you 
still need this, set
+`openejb.ejbd.datasource-metadata=true` on the server. This applies to all 
remote clients.
+
+=== ejbds clients verify the server host name
+
+Clients connecting with `ejbds` now check that the server certificate matches 
the host in the provider URL. A
+certificate without a matching subject alternative name or common name, for 
example when connecting by IP address,
+fails the TLS handshake. Issue certificates for the host names clients use. As 
a temporary measure, start the client
+JVM with `-Dopenejb.client.disableEndpointIdentification=true`. This must be a 
system property of the client JVM, not a
+JNDI property.
+
+=== No transport downgrade for clients
+
+A client configured with `ejbds`, `zejbds` or `https` ignores cluster and 
failover locations with a plain scheme
+(logging a warning) and refuses authentication redirects to a plain scheme. If 
you run a cluster that mixes secure and
+plain transports, configure all members for the secure transport. To restore 
the old behavior, start the client JVM
+with `-Dopenejb.client.allowTransportDowngrade=true`.
+
+=== only_from is authoritative
+
+When a server service sets `only_from`, only the listed hosts may connect. 
Localhost and the server's own address are
+no longer admitted implicitly. Add `localhost` (or `127.0.0.1`) to `only_from` 
if local clients must connect. To restore
+the old behavior, set `openejb.server.only_from.implicit-local=true`.
+
+=== Derby network server binds to localhost
+
+The `derbynet` service ignored its `bind` setting and listened on all 
interfaces. It now honors it, and the default is
+`127.0.0.1`. Remote JDBC clients of the embedded Derby network server (port 
4205) need `-Dderbynet.bind=0.0.0.0` or the
+corresponding setting in the service configuration.
+
+=== Admin port stop requires a secret (OpenEJB standalone)
+
+This only affects OpenEJB standalone (`bin/openejb start`). TomEE does not 
start the admin service, and
+`catalina.sh stop` uses the Tomcat shutdown port as before.
+
+Stop requests on the admin port (4200) must carry a secret. Requests without 
it are refused and the server logs
+`Refused stop request without a valid secret`:
+
+* Set a fixed secret with `openejb.admin.shutdown.secret`. Otherwise the 
server generates one at each start and writes
+  it to `conf/admin-shutdown.secret`, readable only by the server user.
+* `bin/openejb stop` reads the secret from `-s <secret>`, the 
`openejb.admin.shutdown.secret` property or
+  `conf/admin-shutdown.secret`, so it works unchanged for the same user on the 
same machine. To stop the server from
+  another host, use `bin/openejb stop -h <host> -s <secret>`.
+* Custom scripts that send a plain stop byte to port 4200 must send the secret 
as well.
+* To restore the old behavior, set 
`openejb.admin.shutdown.secret.required=false`.
+
+== Filesystem and Passivation
+
+=== Passivation directory
+
+Stateful and managed beans were passivated directly into `java.io.tmpdir`, 
which is `CATALINA_BASE/temp` in TomEE. They
+are now passivated into a private directory 
`${java.io.tmpdir}/openejb-passivation-<random>/`, readable only by the
+server user. A new directory is used at every start and deleted when the JVM 
exits. The startup log shows the directory
+in use.
+
+Passivated state does not survive a restart, which matches the lifecycle of 
stateful beans. If tooling or monitoring
+expects the files in the shared temp directory, set 
`openejb.stateful.passivation.shared-tmpdir=true`. This property
+applies to both stateful and managed beans.
+
+`RAFPassivater` also uses a private temp directory now. There is no switch for 
it.
+
+=== Temp directories and archive extraction
+
+* Internal temp directories (for example for URL caching) are created with 
owner-only permissions. If another OS user
+  needs to read them, adjust your setup.
+* Archives whose entries resolve outside the target directory (for example 
`../` entries) fail to deploy or extract,
+  both in the server and in `tomee-maven-plugin`. Repackage such archives.
+
+== Packaging and Operations
+
+=== Debian packages
+
+The post-install script of the Debian packages no longer makes the 
configuration writable for the `apachetomee`
+service group. `/etc/tomee-<classifier>` and `/var/lib/tomee-<classifier>` are 
now readable but not writable for the
+group, so members of `apachetomee` can no longer edit `server.xml`, 
`tomcat-users.xml`, `tomee.xml` or
+`bin/setenv.sh`. Edit these files as root. The `work` directory, the log 
directory and
+`/var/lib/tomee-<classifier>-user-data` (webapps, temp) remain writable for 
the group.
+
+If an application writes context descriptors to `conf/Catalina/localhost` at 
runtime, grant that directory write access
+yourself.
+
+=== Server info and version output
+
+TomEE no longer patches `catalina.jar` to report its version
+(link:https://issues.apache.org/jira/browse/TOMEE-4710[TOMEE-4710]). The 
server info string is the same as before,
+`Apache Tomcat (TomEE)/<tomcat version> (<tomee version>)`, but it now comes 
from
+`lib/org/apache/catalina/util/ServerInfo.properties`:
+
+* The `tomee.keep-server-info` system property is no longer read. To report 
the plain Tomcat server info, delete
+  `lib/org/apache/catalina/util/ServerInfo.properties`.
+* The bundled jars are no longer repacked, so their signatures and metadata 
are intact.
+
+The startup banner has a new `Git revision` line
+(link:https://issues.apache.org/jira/browse/TOMEE-4709[TOMEE-4709]). Update 
log parsers that rely on the number of banner
+lines.
+
+=== Jars skipped by the scan exclusion list
+
+TomEE now logs the webapp jars it skips because their name matches the 
built-in scan exclusion list. Annotations in
+these jars (`@WebServlet`, `@RolesAllowed`, ...) are ignored. This was already 
the case before, but silently. If the log
+lists a jar that must be scanned, add its name prefix to the 
`openejb.additional.include` system property.
+
+== Configuration Reference
+
+The following switches restore previous behavior. All of them default to the 
secure setting.
+
+[cols="2,1,3",options="header"]
+|===
+|Property|Default|Effect when changed
+|`tomee.security.pbkdf2.allow-weak-parameters`|`false`|`true` accepts stored 
PBKDF2 hashes with weak parameters
+|`openejb.internal.beans.security.enabled`|`true`|`false` allows access to 
internal EJBs without an admin role
+|`openejb.jaxrs.ejb-exception-mapper.expose-message`|`false`|`true` returns 
`EJBException` messages to JAX-RS clients
+|`openejb.ejbd.datasource-metadata`|`false`|`true` allows remote DataSource 
lookups over EJBd
+|`openejb.client.disableEndpointIdentification`|`false`|`true` disables host 
name verification for `ejbds` clients (client JVM)
+|`openejb.client.allowTransportDowngrade`|`false`|`true` lets secure clients 
follow plain failover locations and redirects (client JVM)
+|`openejb.server.only_from.implicit-local`|`false`|`true` admits localhost to 
services restricted with `only_from`
+|`derbynet.bind`|`127.0.0.1`|`0.0.0.0` exposes the Derby network server on all 
interfaces
+|`openejb.admin.shutdown.secret.required`|`true`|`false` accepts stop requests 
without a secret (OpenEJB standalone)
+|`openejb.stateful.passivation.shared-tmpdir`|`false`|`true` passivates 
stateful and managed beans into `java.io.tmpdir`
+|===
diff --git a/src/main/jbake/content/10.3.0/release-notes.adoc 
b/src/main/jbake/content/10.3.0/release-notes.adoc
new file mode 100644
index 0000000..e63888e
--- /dev/null
+++ b/src/main/jbake/content/10.3.0/release-notes.adoc
@@ -0,0 +1,179 @@
+= Apache TomEE 10.3.0 Release Notes
+:index-group: Release Notes
+:jbake-type: page
+:jbake-status: published
+
+We are excited to announce the release of Apache TomEE 10.3.0!
+
+This release on the TomEE 10 / Jakarta EE 10 line focuses on security 
hardening. Alongside the fixes tracked in Jira, we
+reviewed large parts of the code base and tightened the defaults of 
authentication, remote EJB, web services, passivation
+and build tooling. TomEE 10.3.0 also removes several legacy modules 
(`openejb-hessian`, `openejb-ssh`,
+`openejb-common-cli` and the standalone HTTP server of `openejb-http`), moves 
the Maven and Gradle plugins to current
+build tool APIs, and upgrades Tomcat to 10.1.61 along with many other 
dependencies.
+
+IMPORTANT: Several of these changes are not backwards compatible. Please read 
the link:migration-guide.html[TomEE 10.3.0 Migration Guide]
+before upgrading from TomEE 10.2.x or earlier.
+
+We extend our deepest gratitude to everyone who contributed to this release, 
especially our incredible volunteers
+who worked on TomEE 10 and on fixes in our upstream dependencies such as 
Tomcat, OWB, CXF, MyFaces, and more.
+
+Your efforts made TomEE 10.3.0 possible!
+
+== Security Hardening
+
+The following changes were made without dedicated Jira issues. Items marked 
*(breaking)* are covered in the
+link:migration-guide.html[migration guide].
+
+=== MicroProfile JWT
+
+[.compact]
+- The MP-JWT filter is only registered for applications using 
`@LoginConfig(authMethod = "MP-JWT")`. Other authentication methods no longer 
trigger JWT processing *(breaking)*.
+- `@RolesAllowed` constraints are resolved per resource class. Methods 
inherited by several resource classes no longer merge their roles, and an empty 
`@RolesAllowed({})` now denies all callers *(breaking)*.
+- The caller identity is restored when the filter chain throws, so it cannot 
leak into a later request on a pooled thread.
+- A negative `mp.jwt.verify.clock.skew` now fails the deployment instead of 
silently disabling the token expiry check *(breaking)*.
+
+=== Authentication and Identity Stores
+
+[.compact]
+- The LDAP identity store escapes caller names in search filters and DNs, and 
no longer attempts a bind with an empty password (anonymous bind) *(breaking)*.
+- `SQLLoginModule` rejects users with a `NULL` stored password. 
`SQLLoginModule` and `PropertiesLoginModule` compare passwords in constant time 
and report a single generic failure message *(breaking)*.
+- `TomEEPbkdf2PasswordHash` validates the algorithm and iteration count of 
stored hashes and rejects weak parameters *(breaking)*.
+- The Tomcat user identity store verifies passwords through the 
`CredentialHandler` of the matching `UserDatabaseRealm`, so digested passwords 
in `tomcat-users.xml` work as expected *(breaking)*.
+- A caller principal is no longer granted a role just because its name matches 
the role name *(breaking)*.
+- Remember-me tokens are removed from the `RememberMeIdentityStore` on logout.
+- OpenID Connect `state` and `nonce` values are generated with `SecureRandom`, 
and `state` is compared in constant time.
+- Using the `Static3DES` password cipher logs a warning that it only 
obfuscates passwords.
+
+=== Authorization
+
+[.compact]
+- EJB method permissions (`@RolesAllowed`, `@DenyAll`) are evaluated through 
the installed JACC policy on all JDKs again. TomEE 10.2.0 skipped this check on 
Java 21 and newer *(breaking)*.
+- Internal EJBs such as the Deployer always require the `tomee-admin` or 
`openejb-admin` role, and TomEE no longer creates a default `tomee`/`tomee` 
admin user *(breaking)*.
+- Fixed a `StackOverflowError` in the JACC `PolicyConfigurationFactory`.
+
+=== Web Services, JAX-RS and Routing
+
+[.compact]
+- Security constraints generated for JAX-WS endpoints protect all HTTP methods 
instead of only `GET` and `POST` *(breaking)*.
+- EJB web services packaged in a WAR now enforce the `auth-method` configured 
in `openejb-jar.xml` *(breaking)*.
+- The WS-Security caller identity is cleared after each JAX-WS request, 
including on faults.
+- The default JAX-RS mapper for `EJBException` no longer returns the exception 
message to the client *(breaking)*.
+- `RouterValve` validates forward targets: it refuses `WEB-INF`/`META-INF` 
targets and honors the webapp's security constraints *(breaking)*.
+
+=== Remote EJB and Server Services
+
+[.compact]
+- Remote lookups of DataSources over EJBd are disabled by default *(breaking)*.
+- `ejbds` clients verify that the server certificate matches the host name 
*(breaking)*.
+- Clients configured for a secure transport ignore failover locations and 
refuse redirects that downgrade to a plain transport *(breaking)*.
+- `only_from` is authoritative for server services: localhost is no longer 
admitted implicitly *(breaking)*.
+- The Derby network server honors its `bind` setting (default `127.0.0.1`) 
*(breaking)*.
+- Stop requests on the standalone admin port require a shared secret 
*(breaking)*.
+- Primary keys of stateful and managed beans are random `UUID` values.
+
+=== Filesystem and Passivation
+
+[.compact]
+- Stateful and managed beans are passivated to a private, owner-only directory 
instead of the shared temp directory *(breaking)*.
+- `RAFPassivater` keeps its file in a private temp directory and reads back 
the data it wrote correctly.
+- Session ids that would resolve outside the passivation directory are 
rejected.
+- Internal temp directories are created atomically with owner-only permissions.
+- Archive extraction (WAR/EAR deployment, provisioning and 
`tomee-maven-plugin`) rejects entries that escape the target directory.
+- XML parsing of Maven metadata and `settings.xml` used for `mvn:` 
provisioning disables DTDs and external entities.
+
+=== Build Tooling and Packaging
+
+[.compact]
+- `tomee-maven-plugin` warns when it sends credentials over plain HTTP to a 
non-local host.
+- The LiveReload connector of `tomee-embedded-maven-plugin` binds to 
`localhost` and checks the WebSocket `Origin` header *(breaking)*.
+- The `quickSession` option of the Maven, Gradle and embedded tooling defaults 
to `false`, so session ids are always generated with `SecureRandom` 
*(breaking)*.
+- The Debian packages keep the configuration read-only for the `apachetomee` 
service group *(breaking)*.
+- The systemd service example in the documentation runs TomEE as a dedicated 
user.
+- Webapp jars skipped by the built-in scan exclusion list are now logged, so 
annotations that are silently ignored become visible.
+- The optional log4j 1.x API dependency (EOL log4j 1.2.17) is replaced by 
reload4j.
+
+== Bug
+
+[.compact]
+- link:https://issues.apache.org/jira/browse/TOMEE-2044[TOMEE-2044] 
threadPool-queue (in ServicePool) from ejbd-Service is never processed
+- link:https://issues.apache.org/jira/browse/TOMEE-3726[TOMEE-3726] Queue is 
visible in JNDI Tree (java://id-resource)
+- link:https://issues.apache.org/jira/browse/TOMEE-4011[TOMEE-4011] 
Multi-threaded Deployment of multiple war-files runs in TomEERuntimeException
+- link:https://issues.apache.org/jira/browse/TOMEE-4029[TOMEE-4029] Use of 
JWKS forces kid to be present in JWTs
+- link:https://issues.apache.org/jira/browse/TOMEE-4240[TOMEE-4240] The 
implementation for mail.mime.parameters.strict parameter is missing in 
jakarta/mail/internet/ParameterList.java class of 
geronimo-mail_2.1_spec-1.0.0-M1.jar in TomEE 9.1.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4438[TOMEE-4438] Disable 
releases for apache-snapshot repo
+- link:https://issues.apache.org/jira/browse/TOMEE-4547[TOMEE-4547] 
MultipartMessage not build correctly with Jakarta.mail / Interferes with 
Geronimo-mail
+- link:https://issues.apache.org/jira/browse/TOMEE-4642[TOMEE-4642] Deployment 
fails when a war lists a servlet or filter class it does not package
+- link:https://issues.apache.org/jira/browse/TOMEE-4651[TOMEE-4651] TomEE does 
not register jakarta.tags.* TLD URIs, breaking all Jakarta Tags 3.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4655[TOMEE-4655] A failed 
CDI/EJB deployment leaks its deployment ID into later apps
+- link:https://issues.apache.org/jira/browse/TOMEE-4682[TOMEE-4682] 
SecurityContext.authenticate() does not persist the session (bypasses 
HttpServletRequest.authenticate())
+- link:https://issues.apache.org/jira/browse/TOMEE-4699[TOMEE-4699] 
ThreadContext constructor is not thread-safe, causing loss of submitted tasks.
+- link:https://issues.apache.org/jira/browse/TOMEE-4703[TOMEE-4703] 
ApplicationThreadContextProvider stores a live ThreadContext reference instead 
of an immutable snapshot
+- link:https://issues.apache.org/jira/browse/TOMEE-4704[TOMEE-4704] 
CUTask.invoke() does not safely propagate errors to ManagedTask
+- link:https://issues.apache.org/jira/browse/TOMEE-4708[TOMEE-4708] OpenID 
definition EL expressions are evaluated on a shared ELProcessor and fail under 
concurrent requests (regression of TOMEE-4595)
+- link:https://issues.apache.org/jira/browse/TOMEE-4712[TOMEE-4712] MDB 
endpoints are activated before the application's other EJBs are started
+- link:https://issues.apache.org/jira/browse/TOMEE-4714[TOMEE-4714] 
TomEEEmbeddedExtension (JUnit 5) can not start the container again after it was 
closed
+- link:https://issues.apache.org/jira/browse/TOMEE-4715[TOMEE-4715] TomEE 
embedded application runner does not inject @Resource into the @Application 
descriptor
+- link:https://issues.apache.org/jira/browse/TOMEE-4716[TOMEE-4716] 
MicroProfile Health endpoints are not deployed when the webapp declares a 
JAX-RS Application subclass
+- link:https://issues.apache.org/jira/browse/TOMEE-4728[TOMEE-4728] 
MicroProfile Health endpoint runs the providers of a declared JAX-RS application
+- link:https://issues.apache.org/jira/browse/TOMEE-4729[TOMEE-4729] MP-JWT 
security state is not restored for asynchronous requests
+- link:https://issues.apache.org/jira/browse/TOMEE-4730[TOMEE-4730] MP-JWT 
ignores class-level security annotations of a resource superclass
+- link:https://issues.apache.org/jira/browse/TOMEE-4731[TOMEE-4731] 
TxThreadContextRestorer fails with NPE when managed threads end after the 
container shut down
+
+== Improvement
+
+[.compact]
+- link:https://issues.apache.org/jira/browse/TOMEE-1619[TOMEE-1619] Add 
exception message to Alerts
+- link:https://issues.apache.org/jira/browse/TOMEE-4662[TOMEE-4662] Speed up 
annotation processing during WAR deploy
+- link:https://issues.apache.org/jira/browse/TOMEE-4709[TOMEE-4709] Track git 
revision in version info
+- link:https://issues.apache.org/jira/browse/TOMEE-4710[TOMEE-4710] Don't 
patch catalina.jar just to print TomEE Version
+
+== Task
+
+[.compact]
+- link:https://issues.apache.org/jira/browse/TOMEE-4700[TOMEE-4700] Drop 
openejb-hessian
+- link:https://issues.apache.org/jira/browse/TOMEE-4701[TOMEE-4701] Drop 
openejb-ssh
+- link:https://issues.apache.org/jira/browse/TOMEE-4702[TOMEE-4702] Drop 
openejb-common-cli
+- link:https://issues.apache.org/jira/browse/TOMEE-4705[TOMEE-4705] Migrate 
the Maven plugins off the Maven 2 API
+- link:https://issues.apache.org/jira/browse/TOMEE-4706[TOMEE-4706] Migrate 
the Gradle plugin to a current Gradle version
+- link:https://issues.apache.org/jira/browse/TOMEE-4707[TOMEE-4707] Drop the 
standalone HTTP server from openejb-http
+- link:https://issues.apache.org/jira/browse/TOMEE-4733[TOMEE-4733] Pin 
Surefire to 3.5.x in TCK modules
+
+== Documentation
+
+[.compact]
+- link:https://issues.apache.org/jira/browse/TOMEE-4673[TOMEE-4673] Remove 
"About the 'tomee' webapp" since Tomee drop-in webapp was removed in TOMEE-3724
+
+== Dependency upgrade
+
+[.compact]
+- link:https://issues.apache.org/jira/browse/TOMEE-4687[TOMEE-4687] 
actions/setup-java 6.0.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4671[TOMEE-4671] Apache 
ActiveMQ 6.2.8
+- link:https://issues.apache.org/jira/browse/TOMEE-4694[TOMEE-4694] Apache 
ActiveMQ 6.2.10
+- link:https://issues.apache.org/jira/browse/TOMEE-4721[TOMEE-4721] Apache 
ActiveMQ 6.3.3
+- link:https://issues.apache.org/jira/browse/TOMEE-4680[TOMEE-4680] Apache CXF 
- CVE-2026-54225 in TomEE 10.2.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4664[TOMEE-4664] Apache 
Neethi 3.2.3
+- link:https://issues.apache.org/jira/browse/TOMEE-4724[TOMEE-4724] Apache 
Neethi 3.2.4
+- link:https://issues.apache.org/jira/browse/TOMEE-4672[TOMEE-4672] 
Bouncycastle 1.86
+- link:https://issues.apache.org/jira/browse/TOMEE-4669[TOMEE-4669] 
commons-codec 1.23.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4726[TOMEE-4726] 
commons-lang3 3.21.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4676[TOMEE-4676] CXF 4.1.9
+- link:https://issues.apache.org/jira/browse/TOMEE-4663[TOMEE-4663] Geronimo 
Mail 1.1.1
+- link:https://issues.apache.org/jira/browse/TOMEE-4696[TOMEE-4696] Hibernate 
ORM 6.6.56.Final
+- link:https://issues.apache.org/jira/browse/TOMEE-4683[TOMEE-4683] Jackson 
2.22.2
+- link:https://issues.apache.org/jira/browse/TOMEE-4723[TOMEE-4723] Jackson 
2.22.4
+- link:https://issues.apache.org/jira/browse/TOMEE-4684[TOMEE-4684] Johnzon 
2.2.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4719[TOMEE-4719] Jose4j 
0.9.7
+- link:https://issues.apache.org/jira/browse/TOMEE-4685[TOMEE-4685] JUnit 6.1.3
+- link:https://issues.apache.org/jira/browse/TOMEE-4666[TOMEE-4666] Mojarra 
4.0.20
+- link:https://issues.apache.org/jira/browse/TOMEE-4695[TOMEE-4695] Mojarra 
4.0.28
+- link:https://issues.apache.org/jira/browse/TOMEE-4718[TOMEE-4718] MyFaces 
4.0.4
+- link:https://issues.apache.org/jira/browse/TOMEE-4698[TOMEE-4698] Plexus 
Archiver 4.14.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4722[TOMEE-4722] SLF4J 
2.0.20
+- link:https://issues.apache.org/jira/browse/TOMEE-4668[TOMEE-4668] SmallRye 
Config 3.18.1
+- link:https://issues.apache.org/jira/browse/TOMEE-4686[TOMEE-4686] SmallRye 
Config 3.18.2
+- link:https://issues.apache.org/jira/browse/TOMEE-4720[TOMEE-4720] Snakeyaml 
2.7
+- link:https://issues.apache.org/jira/browse/TOMEE-4677[TOMEE-4677] Tomcat 
10.1.61
+- link:https://issues.apache.org/jira/browse/TOMEE-4678[TOMEE-4678] Upgrade 
micrometer-core jar
+- link:https://issues.apache.org/jira/browse/TOMEE-4725[TOMEE-4725] WSS4J 4.0.2
+- link:https://issues.apache.org/jira/browse/TOMEE-4697[TOMEE-4697] XBean 5.0.0
+
diff --git a/src/main/jbake/content/11.0.0-M2/migration-guide.adoc 
b/src/main/jbake/content/11.0.0-M2/migration-guide.adoc
new file mode 100644
index 0000000..ef851bb
--- /dev/null
+++ b/src/main/jbake/content/11.0.0-M2/migration-guide.adoc
@@ -0,0 +1,422 @@
+= Migrating to Apache TomEE 11.0.0-M2
+:index-group: Release Notes
+:jbake-type: page
+:jbake-status: published
+:toc:
+
+TomEE 11.0.0-M2 contains a large number of security hardening changes. Many of 
them tighten defaults that earlier TomEE
+versions left open, so applications and deployments that relied on the old 
behavior need to be adjusted. This guide
+lists every change that can affect an upgrade from TomEE 11.0.0-M1, explains 
who is affected, and shows what to change.
+TomEE 10.3.0 received the same hardening, so the guide also applies when you 
move from TomEE 10.2.x or earlier to
+TomEE 11, in addition to the Jakarta EE 11 changes.
+Where TomEE offers a switch to restore the previous behavior, it is listed as 
well. Use these switches only as a
+temporary measure: they re-open the issue the change fixed.
+
+See the link:release-notes.html[release notes] for the full list of changes.
+
+System properties mentioned in this guide can be set in 
`conf/system.properties` or passed as `-D` options to the JVM,
+unless the section says otherwise.
+
+== Removed Modules
+
+The following modules are no longer built or published. None of them was part 
of a TomEE distribution by default.
+
+[cols="1,2,2",options="header"]
+|===
+|Module|What it provided|Replacement
+|`openejb-hessian` 
(link:https://issues.apache.org/jira/browse/TOMEE-4700[TOMEE-4700])
+|The `hessian` server service exposing `@Remote` EJBs over Hessian, 
`HessianInitialContextFactory` and the CDI `@Hessian` client injection
+|EJBd (`ejbd`/`ejbds`, or EJBd over HTTP at `/tomee/ejb`), JAX-RS or JAX-WS
+|`openejb-ssh` 
(link:https://issues.apache.org/jira/browse/TOMEE-4701[TOMEE-4701])
+|The `ssh` service (port 4222), a JAAS-authenticated administration shell
+|JMX, `tomee-maven-plugin` or remote deployment through the Deployer, the 
`bin/openejb` and `bin/tomee` commands
+|`openejb-common-cli` 
(link:https://issues.apache.org/jira/browse/TOMEE-4702[TOMEE-4702])
+|The command framework behind the SSH shell
+|None needed. The `bin/openejb` commands (`start`, `stop`, `deploy`, `cipher`, 
...) are not affected.
+|`openejb-http` 
(link:https://issues.apache.org/jira/browse/TOMEE-4707[TOMEE-4707])
+|The standalone HTTP server (`httpejbd` service, port 4204) used by OpenEJB 
standalone and embedded containers, including its Jetty backend and the 
embedded JAX-RS/JAX-WS registries
+|TomEE, TomEE embedded or the Arquillian TomEE adapters. EJBd over HTTP is 
available in TomEE at `/tomee/ejb` with `tomee.remote.support=true`.
+|`tomee-webaccess` 
(link:https://issues.apache.org/jira/browse/TOMEE-4634[TOMEE-4634])
+|The `tomee-webaccess` administration war
+|None
+|===
+
+With `tomee-webaccess`, the commented-out `tomee-admin` role and `tomee` user 
are gone from the `conf/tomcat-users.xml`
+of the distributions, and the public 
`Installer.addTomEEAdminConfInTomcatUsers()` method is removed.
+
+Removing `openejb-http` has these further consequences:
+
+* OpenEJB standalone, `ApplicationComposer`, `EJBContainer` and 
`arquillian-openejb-embedded` no longer serve JAX-RS or
+  JAX-WS endpoints over HTTP. The `conf/httpejbd.properties` file, the 
`httpejbd.*` properties and the
+  `--httpejbd-bind`/`--httpejbd-port` options are gone.
+* `@EnableServices` no longer has the `jaxrs`, `jaxws` and `httpDebug` 
attributes, and `@JaxrsProviders` no longer has
+  `applicationName`. Tests that used them need to move to TomEE embedded or 
Arquillian.
+* The `org.apache.openejb.server.httpd.ServerServlet` class is now 
`org.apache.tomee.catalina.remote.ServerServlet`.
+  If your `web.xml` declares this servlet to expose EJBd over HTTP, update the 
class name. `EEFilter`,
+  `BeginWebBeansListener` and `EndWebBeansListener` moved to the 
`org.apache.tomee.catalina` package as well.
+* The default of `openejb.rest.wildcard` changed from `.*` to `*`.
+
+== Build Tools
+
+=== Maven 3.10.0 or newer
+
+The TomEE Maven plugins no longer use the Maven 2 API
+(link:https://issues.apache.org/jira/browse/TOMEE-4705[TOMEE-4705]). 
`tomee-maven-plugin` and the other TomEE Maven
+plugins now require Maven 3.10.0 or newer and Java 17. Plugin coordinates, 
goals and parameters are unchanged.
+
+=== Gradle plugin
+
+The Gradle plugin is built against the current Gradle API
+(link:https://issues.apache.org/jira/browse/TOMEE-4706[TOMEE-4706]) and works 
with Gradle 8.x and 9.x. The plugin id
+`org.apache.tomee.tomee-embedded` and its DSL are unchanged.
+
+=== quickSession defaults to false
+
+The `quickSession` option makes the dev tooling generate session ids with a 
non-secure random generator. It now
+defaults to `false` in:
+
+* `tomee-maven-plugin` (`quickSession`, user property 
`tomee-plugin.quick-session`)
+* `tomee-embedded-maven-plugin` (user property 
`tomee-embedded-plugin.quickSession`)
+* TomEE embedded (`Configuration.quickSession`)
+* the Gradle `tomee-embedded` task (`quickSession`)
+
+Startup can be slightly slower on systems with little entropy. Set the option 
to `true` to restore the previous behavior.
+
+=== LiveReload only listens on localhost
+
+The LiveReload connector of `tomee-embedded-maven-plugin` (port 35729) now 
binds to `localhost` and rejects WebSocket
+handshakes whose `Origin` is not a loopback address. Browser extensions and 
requests without an `Origin` are still
+accepted. If you use LiveReload from another machine, a VM or a container 
host, configure:
+
+[source,xml]
+----
+<liveReload>
+  <host>0.0.0.0</host>
+  <allowAnyOrigin>true</allowAnyOrigin>
+</liveReload>
+----
+
+=== Credentials over plain HTTP
+
+The `tomee-maven-plugin` command goals (`deploy`, `undeploy`, ...) log a 
warning when they send a user and password to a
+non-local host over plain HTTP. Configure an HTTPS port with 
`tomee-plugin.https` and set
+`tomee-plugin.command-force-https=true` to send credentials over HTTPS.
+
+== MicroProfile JWT
+
+=== The MP-JWT filter requires authMethod "MP-JWT"
+
+Before, any class annotated with `@LoginConfig` enabled MP-JWT processing, 
whatever its `authMethod`. Now JWT
+processing is only enabled for:
+
+[source,java]
+----
+@LoginConfig(authMethod = "MP-JWT")
+----
+
+Applications that use a different `authMethod` (for example `BASIC`) and still 
expect bearer tokens to be accepted must
+change it to `MP-JWT`.
+
+=== Role constraints are resolved per resource class
+
+`@RolesAllowed`, `@PermitAll` and `@DenyAll` are now resolved for each 
resource class separately:
+
+* A method inherited by several resource classes no longer gets the union of 
the roles of all these classes. Each class
+  gets the roles declared for it.
+* An empty `@RolesAllowed({})` denies all callers (HTTP 403). Before, it 
allowed everyone. Use `@PermitAll` if the
+  method should be public.
+* An unannotated subclass inherits the class-level annotation of an annotated 
superclass for the methods it inherits
+  (link:https://issues.apache.org/jira/browse/TOMEE-4730[TOMEE-4730]). Such 
endpoints were unprotected before and now
+  return 401 or 403 for callers without the required role. A class carrying 
more than one of these annotations fails
+  the deployment.
+
+Review resources that use inheritance or empty role lists.
+
+=== Negative clock skew is rejected
+
+A negative `mp.jwt.verify.clock.skew` used to disable the expiry check of 
tokens. It now fails the deployment with a
+`DeploymentException`. Set the value to `0` or a positive number of seconds.
+
+== Authentication and Identity Stores
+
+=== LDAP identity store
+
+* Caller names are escaped (RFC 4515) when TomEE builds search filters, and 
DNs built from `callerBaseDn` are escaped
+  as well. If your application escaped caller names itself, remove that code, 
since names would now be escaped twice.
+  Caller names containing `*`, `(`, `)` or `\` no longer act as wildcards or 
filter syntax.
+* A caller with an empty or missing password is rejected without a bind 
attempt. Before, an LDAP server allowing
+  anonymous binds accepted such logins.
+
+=== Login modules
+
+* `SQLLoginModule` rejects users whose stored password is `NULL`. Before, such 
users could log in without a password.
+  Give these users a password or remove them.
+* `PropertiesLoginModule` reports `Username or password does not match` for 
both an unknown user and a wrong password.
+  Update anything that parses the old messages.
+
+=== PBKDF2 password hashes
+
+`TomEEPbkdf2PasswordHash` now only accepts the algorithms 
`PBKDF2WithHmacSHA1`, `PBKDF2WithHmacSHA224`,
+`PBKDF2WithHmacSHA256`, `PBKDF2WithHmacSHA384` and `PBKDF2WithHmacSHA512` with 
at least 1024 iterations, both for new
+hashes and for stored hashes:
+
+* Logins whose stored hash uses fewer iterations or another algorithm fail, 
and TomEE logs a warning once.
+* `Pbkdf2PasswordHash.Algorithm` or `Pbkdf2PasswordHash.Iterations` parameters 
outside these limits make the
+  initialization fail with an `IllegalArgumentException`.
+* Malformed stored hashes fail the login instead of throwing an exception.
+
+Rehash affected passwords with stronger parameters. As a temporary measure, 
set the system property
+`tomee.security.pbkdf2.allow-weak-parameters=true` to accept weak stored 
hashes. TomEE then logs a warning for each
+weak parameter combination it accepts.
+
+=== Tomcat user identity store
+
+The identity store behind `@TomcatUserIdentityStoreDefinition` now checks 
passwords with the `CredentialHandler` of the
+`UserDatabaseRealm` in `conf/server.xml` that uses the same user database 
resource:
+
+* Passwords stored as digests in `tomcat-users.xml` are verified against the 
password the user enters. Sending the
+  stored digest itself no longer works.
+* A wrong password results in `INVALID` instead of `NOT_VALIDATED`.
+* If no matching realm is found, TomEE compares passwords as plain text and 
logs a warning.
+
+Make sure the `CredentialHandler` of the realm matches the format of the 
passwords in `tomcat-users.xml`.
+
+=== Principal names are no longer mapped to roles
+
+A user authenticated by a Tomcat realm was implicitly given a role with the 
same name as the user (for example user
+`admin` got role `admin`). This no longer happens: roles come only from the 
realm. Group principals are still mapped
+by name. If your application relied on this, assign the role to the user in 
the realm.
+
+=== Static3DES password cipher
+
+Using the `Static3DES` password cipher for resource passwords logs a warning: 
it uses a key shipped with TomEE and
+only obfuscates the password. Nothing breaks, but consider a custom 
`PasswordCipher` or a `cdi:` cipher.
+
+== Authorization
+
+=== Jakarta Authorization 3.0
+
+The Jakarta Authorization 3.0 implementation is complete. This changes how 
TomEE enforces EJB method permissions:
+
+* On Java 21 and newer, TomEE 11.0.0-M1 skipped the JACC check for EJB method 
permissions and logged
+  `Skipping JACC authorization checks as TomEE running on JDK 21+`. All 
callers could invoke EJBs regardless of
+  `@RolesAllowed` and `@DenyAll`. TomEE 11.0.0-M2 evaluates them through 
`jakarta.security.jacc.PolicyFactory` on all
+  JDKs, so callers without the required role now get an `EJBAccessException`. 
Check the role assignments of your users
+  and the `@RolesAllowed` annotations of your EJBs. If no policy is installed, 
EJB access is denied.
+* A custom provider configured with `jakarta.security.jacc.policy.provider` 
must implement
+  `jakarta.security.jacc.Policy`. A `java.security.Policy` class (such as 
`sun.security.provider.PolicyFile`) makes the
+  startup fail with `Could not install JACC Policy Provider`.
+* The internal classes `PolicyJDK24` and `JaccProvider.Policy` are removed.
+* The `**` role (any authenticated user) is supported.
+* Web security constraints from `web.xml` and `@ServletSecurity` are installed 
as JACC permissions for every deployment,
+  including applications dropped into `webapps/`.
+
+=== Internal EJBs require an admin role
+
+Internal EJBs such as the Deployer (`openejb/DeployerBusinessRemote`) and 
`ConfigurationInfo` always require the
+`tomee-admin` or `openejb-admin` role. Before, the check was skipped in the 
default `development` profile. TomEE also
+no longer creates a `tomee`/`tomee` user with the `tomee-admin` role when 
`tomcat-users.xml` is empty.
+
+Remote deployment, for example with the `tomee-maven-plugin` deploy goals, now 
needs a user with one of these roles in
+`conf/tomcat-users.xml`:
+
+[source,xml]
+----
+<role rolename="tomee-admin"/>
+<user username="deployer" password="..." roles="tomee-admin"/>
+----
+
+The Arquillian remote adapter, `RemoteTomEEEJBContainer` and 
`tomee-maven-plugin` with `reloadOnUpdate` disable the
+check themselves for the servers they start. To disable it for a server, set
+`openejb.internal.beans.security.enabled=false`.
+
+== Web Services, JAX-RS and Routing
+
+=== JAX-WS endpoints protect all HTTP methods
+
+The security constraint TomEE generates for EJB web services with an 
`auth-method` used to cover only `GET` and `POST`.
+It now covers all HTTP methods and denies uncovered methods. `PUT`, `DELETE`, 
`OPTIONS` and other methods now require
+authentication as well. There is no switch to restore the old behavior.
+
+=== EJB web services in a WAR enforce their auth-method
+
+EJB web services packaged in a WAR were published without applying the 
`<web-service-security>` settings
+(`auth-method`, `transport-guarantee`, `realm-name`) from `openejb-jar.xml`. 
They are now enforced:
+
+* Unauthenticated calls, including `?wsdl` requests, get HTTP 401.
+* An `auth-method` other than `BASIC`, `DIGEST`, `CLIENT-CERT` or `NONE` fails 
the deployment.
+* If the webapp has its own `login-config` with a different method, the webapp 
setting wins and TomEE logs a warning.
+
+Set `<auth-method>NONE</auth-method>` (or remove it) for endpoints that are 
meant to be public. Role names are still
+configured with `tomee.jaxws.security-role.<context name>`.
+
+=== JAX-RS responses for EJBException
+
+When an `EJBException` has no mapper of its own, the default JAX-RS mapper 
used to return the exception message as a
+`text/plain` body. It now returns an empty HTTP 500 response and logs the 
message on the server. Exceptions whose cause
+has a mapper are not affected.
+
+If clients parse the error body, register your own `ExceptionMapper`. As a 
temporary measure, set
+`openejb.jaxrs.ejb-exception-mapper.expose-message=true` to restore the old 
body.
+
+=== RouterValve forwards
+
+Forward routes in `WEB-INF/tomee-router.conf` are normalized and checked 
before forwarding:
+
+* Targets that are not absolute paths, cannot be decoded or point into 
`WEB-INF` or `META-INF` get HTTP 404.
+* Targets protected by a security constraint the caller does not satisfy get 
HTTP 403. Before, the forward bypassed
+  the constraint.
+
+Redirect routes are not affected.
+
+== Remote EJB and Server Services
+
+=== Remote DataSource lookup is disabled
+
+Remote clients could look up a DataSource over EJBd and receive its connection 
details, including database
+credentials. This is now refused with a `NamingException` (`Remote DataSource 
lookup is disabled`), for `ejbd`, `ejbds`
+and EJBd over HTTP. Remote EJB calls are not affected.
+
+Clients should not connect to the database with server credentials. If you 
still need this, set
+`openejb.ejbd.datasource-metadata=true` on the server. This applies to all 
remote clients.
+
+=== ejbds clients verify the server host name
+
+Clients connecting with `ejbds` now check that the server certificate matches 
the host in the provider URL. A
+certificate without a matching subject alternative name or common name, for 
example when connecting by IP address,
+fails the TLS handshake. Issue certificates for the host names clients use. As 
a temporary measure, start the client
+JVM with `-Dopenejb.client.disableEndpointIdentification=true`. This must be a 
system property of the client JVM, not a
+JNDI property.
+
+=== No transport downgrade for clients
+
+A client configured with `ejbds`, `zejbds` or `https` ignores cluster and 
failover locations with a plain scheme
+(logging a warning) and refuses authentication redirects to a plain scheme. If 
you run a cluster that mixes secure and
+plain transports, configure all members for the secure transport. To restore 
the old behavior, start the client JVM
+with `-Dopenejb.client.allowTransportDowngrade=true`.
+
+=== only_from is authoritative
+
+When a server service sets `only_from`, only the listed hosts may connect. 
Localhost and the server's own address are
+no longer admitted implicitly. Add `localhost` (or `127.0.0.1`) to `only_from` 
if local clients must connect. To restore
+the old behavior, set `openejb.server.only_from.implicit-local=true`.
+
+=== Derby network server binds to localhost
+
+The `derbynet` service ignored its `bind` setting and listened on all 
interfaces. It now honors it, and the default is
+`127.0.0.1`. Remote JDBC clients of the embedded Derby network server (port 
4205) need `-Dderbynet.bind=0.0.0.0` or the
+corresponding setting in the service configuration.
+
+=== Admin port stop requires a secret (OpenEJB standalone)
+
+This only affects OpenEJB standalone (`bin/openejb start`). TomEE does not 
start the admin service, and
+`catalina.sh stop` uses the Tomcat shutdown port as before.
+
+Stop requests on the admin port (4200) must carry a secret. Requests without 
it are refused and the server logs
+`Refused stop request without a valid secret`:
+
+* Set a fixed secret with `openejb.admin.shutdown.secret`. Otherwise the 
server generates one at each start and writes
+  it to `conf/admin-shutdown.secret`, readable only by the server user.
+* `bin/openejb stop` reads the secret from `-s <secret>`, the 
`openejb.admin.shutdown.secret` property or
+  `conf/admin-shutdown.secret`, so it works unchanged for the same user on the 
same machine. To stop the server from
+  another host, use `bin/openejb stop -h <host> -s <secret>`.
+* Custom scripts that send a plain stop byte to port 4200 must send the secret 
as well.
+* To restore the old behavior, set 
`openejb.admin.shutdown.secret.required=false`.
+
+== Filesystem and Passivation
+
+=== Passivation directory
+
+Stateful and managed beans were passivated directly into `java.io.tmpdir`, 
which is `CATALINA_BASE/temp` in TomEE. They
+are now passivated into a private directory 
`${java.io.tmpdir}/openejb-passivation-<random>/`, readable only by the
+server user. A new directory is used at every start and deleted when the JVM 
exits. The startup log shows the directory
+in use.
+
+Passivated state does not survive a restart, which matches the lifecycle of 
stateful beans. If tooling or monitoring
+expects the files in the shared temp directory, set 
`openejb.stateful.passivation.shared-tmpdir=true`. This property
+applies to both stateful and managed beans.
+
+`RAFPassivater` also uses a private temp directory now. There is no switch for 
it.
+
+=== Temp directories and archive extraction
+
+* Internal temp directories (for example for URL caching) are created with 
owner-only permissions. If another OS user
+  needs to read them, adjust your setup.
+* Archives whose entries resolve outside the target directory (for example 
`../` entries) fail to deploy or extract,
+  both in the server and in `tomee-maven-plugin`. Repackage such archives.
+
+== Jakarta Data
+
+Dynamic `Sort` properties passed to repository methods must be attribute names 
or dotted attribute paths, such as
+`name` or `address.city`. Anything else, for example `lower(name)`, throws an 
`IllegalArgumentException`
+(`Invalid sort property`). Validate or map sort input from clients to 
attribute names before passing it to the
+repository.
+
+== Persistence Providers
+
+=== EclipseLink in TomEE Plume
+
+TomEE Plume ships the modular EclipseLink artifacts 
(`org.eclipse.persistence.core`,
+`org.eclipse.persistence.jpa`, `org.eclipse.persistence.jpa.jpql`) instead of 
the `eclipselink` uber jar
+(link:https://issues.apache.org/jira/browse/TOMEE-4657[TOMEE-4657]). MOXy, 
SDO, JPA-RS and the Oracle database
+platform extensions are no longer part of Plume, and the JAXB reference 
implementation is the only JAXB provider. This
+fixes Bean Validation XML configuration on Plume. Applications that use MOXy 
or the other removed EclipseLink modules
+must package them in the application.
+
+=== OpenJPA next to the TomEE BOM
+
+TomEE 11.0.0-M2 uses XBean 5.0.0. Projects that add 
`org.apache.openjpa:openjpa` next to the TomEE BOM may need to
+exclude `org.apache.xbean:xbean-asm9-shaded` from the OpenJPA dependency, as 
the TomEE examples do.
+
+== Packaging and Operations
+
+=== Debian packages
+
+The post-install script of the Debian packages no longer makes the 
configuration writable for the `apachetomee`
+service group. `/etc/tomee-<classifier>` and `/var/lib/tomee-<classifier>` are 
now readable but not writable for the
+group, so members of `apachetomee` can no longer edit `server.xml`, 
`tomcat-users.xml`, `tomee.xml` or
+`bin/setenv.sh`. Edit these files as root. The `work` directory, the log 
directory and
+`/var/lib/tomee-<classifier>-user-data` (webapps, temp) remain writable for 
the group.
+
+If an application writes context descriptors to `conf/Catalina/localhost` at 
runtime, grant that directory write access
+yourself.
+
+=== Server info and version output
+
+TomEE no longer patches `catalina.jar` to report its version
+(link:https://issues.apache.org/jira/browse/TOMEE-4710[TOMEE-4710]). The 
server info string is the same as before,
+`Apache Tomcat (TomEE)/<tomcat version> (<tomee version>)`, but it now comes 
from
+`lib/org/apache/catalina/util/ServerInfo.properties`:
+
+* The `tomee.keep-server-info` system property is no longer read. To report 
the plain Tomcat server info, delete
+  `lib/org/apache/catalina/util/ServerInfo.properties`.
+* The bundled jars are no longer repacked, so their signatures and metadata 
are intact.
+
+The startup banner has a new `Git revision` line
+(link:https://issues.apache.org/jira/browse/TOMEE-4709[TOMEE-4709]). Update 
log parsers that rely on the number of banner
+lines.
+
+=== Jars skipped by the scan exclusion list
+
+TomEE now logs the webapp jars it skips because their name matches the 
built-in scan exclusion list. Annotations in
+these jars (`@WebServlet`, `@RolesAllowed`, ...) are ignored. This was already 
the case before, but silently. If the log
+lists a jar that must be scanned, add its name prefix to the 
`openejb.additional.include` system property.
+
+== Configuration Reference
+
+The following switches restore previous behavior. All of them default to the 
secure setting.
+
+[cols="2,1,3",options="header"]
+|===
+|Property|Default|Effect when changed
+|`tomee.security.pbkdf2.allow-weak-parameters`|`false`|`true` accepts stored 
PBKDF2 hashes with weak parameters
+|`openejb.internal.beans.security.enabled`|`true`|`false` allows access to 
internal EJBs without an admin role
+|`openejb.jaxrs.ejb-exception-mapper.expose-message`|`false`|`true` returns 
`EJBException` messages to JAX-RS clients
+|`openejb.ejbd.datasource-metadata`|`false`|`true` allows remote DataSource 
lookups over EJBd
+|`openejb.client.disableEndpointIdentification`|`false`|`true` disables host 
name verification for `ejbds` clients (client JVM)
+|`openejb.client.allowTransportDowngrade`|`false`|`true` lets secure clients 
follow plain failover locations and redirects (client JVM)
+|`openejb.server.only_from.implicit-local`|`false`|`true` admits localhost to 
services restricted with `only_from`
+|`derbynet.bind`|`127.0.0.1`|`0.0.0.0` exposes the Derby network server on all 
interfaces
+|`openejb.admin.shutdown.secret.required`|`true`|`false` accepts stop requests 
without a secret (OpenEJB standalone)
+|`openejb.stateful.passivation.shared-tmpdir`|`false`|`true` passivates 
stateful and managed beans into `java.io.tmpdir`
+|===
diff --git a/src/main/jbake/content/11.0.0-M2/release-notes.adoc 
b/src/main/jbake/content/11.0.0-M2/release-notes.adoc
new file mode 100644
index 0000000..649369d
--- /dev/null
+++ b/src/main/jbake/content/11.0.0-M2/release-notes.adoc
@@ -0,0 +1,218 @@
+= Apache TomEE 11.0.0-M2 Release Notes
+:index-group: Release Notes
+:jbake-type: page
+:jbake-status: published
+
+This is the second milestone release of TomEE 11 targeting Jakarta EE 11 and 
MicroProfile 7.1.
+
+Besides the fixes tracked in Jira, this milestone contains a large security 
hardening effort. We reviewed large parts of
+the code base and tightened the defaults of authentication, authorization, 
remote EJB, web services, passivation and build
+tooling. The Jakarta Authorization 3.0 implementation is now complete. This 
milestone also removes several legacy modules
+(`openejb-hessian`, `openejb-ssh`, `openejb-common-cli`, `tomee-webaccess` and 
the standalone HTTP server of
+`openejb-http`), moves the Maven and Gradle plugins to current build tool 
APIs, and upgrades Tomcat to 11.0.27 along
+with many other dependencies.
+
+IMPORTANT: Several of these changes are not backwards compatible. Please read 
the link:migration-guide.html[TomEE 11.0.0-M2 Migration Guide]
+before upgrading from TomEE 11.0.0-M1 or TomEE 10.
+
+Thanks to everyone who contributed code to make this happen.
+
+We would like to highlight and give a shout-out to all our volunteers who have 
been doing the hard work for EE11, which is also being done in all our upstream 
dependencies such as Tomcat, OWB, CXF, MyFaces, etc.
+
+Notable changes:
+
+- Security hardening across the server, summarized below
+- Jakarta Authorization 3.0 is fully implemented, and EJB method permissions 
are enforced on all JDKs
+- TomEE Plume ships the modular EclipseLink JPA artifact instead of the 
`eclipselink` uber jar
+- OpenJPA is still on its TomEE 10 level - the JPA 3.2 PR is not yet included
+
+Please note that we do not pass the full Jakarta EE TCK, nor do we have a 
fully functional TCK setup at the moment. However, our own full build is green.
+
+Please also note the 11.0.0-M2 release is a milestone release intended for 
evaluation purposes and should not be used in production.
+
+== Security Hardening
+
+The following changes were made without dedicated Jira issues. Items marked 
*(breaking)* are covered in the
+link:migration-guide.html[migration guide].
+
+=== MicroProfile JWT
+
+[.compact]
+- The MP-JWT filter is only registered for applications using 
`@LoginConfig(authMethod = "MP-JWT")`. Other authentication methods no longer 
trigger JWT processing *(breaking)*.
+- `@RolesAllowed` constraints are resolved per resource class. Methods 
inherited by several resource classes no longer merge their roles, and an empty 
`@RolesAllowed({})` now denies all callers *(breaking)*.
+- The caller identity is restored when the filter chain throws, so it cannot 
leak into a later request on a pooled thread.
+- A negative `mp.jwt.verify.clock.skew` now fails the deployment instead of 
silently disabling the token expiry check *(breaking)*.
+
+=== Authentication and Identity Stores
+
+[.compact]
+- The LDAP identity store escapes caller names in search filters and DNs, and 
no longer attempts a bind with an empty password (anonymous bind) *(breaking)*.
+- `SQLLoginModule` rejects users with a `NULL` stored password. 
`SQLLoginModule` and `PropertiesLoginModule` compare passwords in constant time 
and report a single generic failure message *(breaking)*.
+- `TomEEPbkdf2PasswordHash` validates the algorithm and iteration count of 
stored hashes and rejects weak parameters *(breaking)*.
+- The Tomcat user identity store verifies passwords through the 
`CredentialHandler` of the matching `UserDatabaseRealm`, so digested passwords 
in `tomcat-users.xml` work as expected *(breaking)*.
+- A caller principal is no longer granted a role just because its name matches 
the role name *(breaking)*.
+- Remember-me tokens are removed from the `RememberMeIdentityStore` on logout.
+- OpenID Connect `state` and `nonce` values are generated with `SecureRandom`, 
and `state` is compared in constant time.
+- Using the `Static3DES` password cipher logs a warning that it only 
obfuscates passwords.
+
+=== Authorization
+
+[.compact]
+- The Jakarta Authorization 3.0 implementation is complete. EJB method 
permissions are evaluated through `jakarta.security.jacc.PolicyFactory` on all 
JDKs (11.0.0-M1 skipped this check on Java 21 and newer), the `**` role is 
supported, and web constraints are installed as JACC permissions for every 
deployment path *(breaking)*.
+- Internal EJBs such as the Deployer always require the `tomee-admin` or 
`openejb-admin` role, and TomEE no longer creates a default `tomee`/`tomee` 
admin user *(breaking)*.
+
+=== Web Services, JAX-RS and Routing
+
+[.compact]
+- Security constraints generated for JAX-WS endpoints protect all HTTP methods 
instead of only `GET` and `POST` *(breaking)*.
+- EJB web services packaged in a WAR now enforce the `auth-method` configured 
in `openejb-jar.xml` *(breaking)*.
+- The WS-Security caller identity is cleared after each JAX-WS request, 
including on faults.
+- The default JAX-RS mapper for `EJBException` no longer returns the exception 
message to the client *(breaking)*.
+- `RouterValve` validates forward targets: it refuses `WEB-INF`/`META-INF` 
targets and honors the webapp's security constraints *(breaking)*.
+
+=== Remote EJB and Server Services
+
+[.compact]
+- Remote lookups of DataSources over EJBd are disabled by default *(breaking)*.
+- `ejbds` clients verify that the server certificate matches the host name 
*(breaking)*.
+- Clients configured for a secure transport ignore failover locations and 
refuse redirects that downgrade to a plain transport *(breaking)*.
+- `only_from` is authoritative for server services: localhost is no longer 
admitted implicitly *(breaking)*.
+- The Derby network server honors its `bind` setting (default `127.0.0.1`) 
*(breaking)*.
+- Stop requests on the standalone admin port require a shared secret 
*(breaking)*.
+- Primary keys of stateful and managed beans are random `UUID` values.
+
+=== Filesystem and Passivation
+
+[.compact]
+- Stateful and managed beans are passivated to a private, owner-only directory 
instead of the shared temp directory *(breaking)*.
+- `RAFPassivater` keeps its file in a private temp directory and reads back 
the data it wrote correctly.
+- Session ids that would resolve outside the passivation directory are 
rejected.
+- Internal temp directories are created atomically with owner-only permissions.
+- Archive extraction (WAR/EAR deployment, provisioning and 
`tomee-maven-plugin`) rejects entries that escape the target directory.
+- XML parsing of Maven metadata and `settings.xml` used for `mvn:` 
provisioning disables DTDs and external entities.
+
+=== Jakarta Data
+
+[.compact]
+- Dynamic `Sort` properties must be attribute names or dotted attribute paths 
*(breaking)*.
+
+=== Build Tooling and Packaging
+
+[.compact]
+- `tomee-maven-plugin` warns when it sends credentials over plain HTTP to a 
non-local host.
+- The LiveReload connector of `tomee-embedded-maven-plugin` binds to 
`localhost` and checks the WebSocket `Origin` header *(breaking)*.
+- The `quickSession` option of the Maven, Gradle and embedded tooling defaults 
to `false`, so session ids are always generated with `SecureRandom` 
*(breaking)*.
+- The Debian packages keep the configuration read-only for the `apachetomee` 
service group *(breaking)*.
+- The systemd service example in the documentation runs TomEE as a dedicated 
user.
+- Webapp jars skipped by the built-in scan exclusion list are now logged, so 
annotations that are silently ignored become visible.
+- The optional log4j 1.x API dependency (EOL log4j 1.2.17) is replaced by 
reload4j.
+
+== Bug
+
+[.compact]
+- link:https://issues.apache.org/jira/browse/TOMEE-2044[TOMEE-2044] 
threadPool-queue (in ServicePool) from ejbd-Service is never processed
+- link:https://issues.apache.org/jira/browse/TOMEE-2764[TOMEE-2764] Path not 
appended when using UriBuilder.fromUri().path() with file scheme
+- link:https://issues.apache.org/jira/browse/TOMEE-2970[TOMEE-2970] JaxRS 
Server Sent events implementation leaves lots of warning logs
+- link:https://issues.apache.org/jira/browse/TOMEE-3726[TOMEE-3726] Queue is 
visible in JNDI Tree (java://id-resource)
+- link:https://issues.apache.org/jira/browse/TOMEE-3782[TOMEE-3782] 
cdi-request-scope example not working
+- link:https://issues.apache.org/jira/browse/TOMEE-4011[TOMEE-4011] 
Multi-threaded Deployment of multiple war-files runs in TomEERuntimeException
+- link:https://issues.apache.org/jira/browse/TOMEE-4029[TOMEE-4029] Use of 
JWKS forces kid to be present in JWTs
+- link:https://issues.apache.org/jira/browse/TOMEE-4240[TOMEE-4240] The 
implementation for mail.mime.parameters.strict parameter is missing in 
jakarta/mail/internet/ParameterList.java class of 
geronimo-mail_2.1_spec-1.0.0-M1.jar in TomEE 9.1.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4438[TOMEE-4438] Disable 
releases for apache-snapshot repo
+- link:https://issues.apache.org/jira/browse/TOMEE-4547[TOMEE-4547] 
MultipartMessage not build correctly with Jakarta.mail / Interferes with 
Geronimo-mail
+- link:https://issues.apache.org/jira/browse/TOMEE-4589[TOMEE-4589] openejb 
reports an error in web.xml which is wrong
+- link:https://issues.apache.org/jira/browse/TOMEE-4620[TOMEE-4620] Misspelled 
field accesToken in OIDC TokenResponse prevents interoperability with custom 
JSON providers (Jackson)
+- link:https://issues.apache.org/jira/browse/TOMEE-4631[TOMEE-4631] 
arquillian-tomee-remote: static "registered" latch breaks container 
re-registration on a second Arquillian Manager (e.g. failsafe 
rerunFailingTestsCount)
+- link:https://issues.apache.org/jira/browse/TOMEE-4642[TOMEE-4642] Deployment 
fails when a war lists a servlet or filter class it does not package
+- link:https://issues.apache.org/jira/browse/TOMEE-4651[TOMEE-4651] TomEE does 
not register jakarta.tags.* TLD URIs, breaking all Jakarta Tags 3.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4655[TOMEE-4655] A failed 
CDI/EJB deployment leaks its deployment ID into later apps
+- link:https://issues.apache.org/jira/browse/TOMEE-4657[TOMEE-4657] Bean 
Validation XML config fails on stock Plume: MOXy beats JAXB RI in ServiceLoader
+- link:https://issues.apache.org/jira/browse/TOMEE-4674[TOMEE-4674] Using 
otel.config.file in TomEE fails
+- link:https://issues.apache.org/jira/browse/TOMEE-4682[TOMEE-4682] 
SecurityContext.authenticate() does not persist the session (bypasses 
HttpServletRequest.authenticate())
+- link:https://issues.apache.org/jira/browse/TOMEE-4699[TOMEE-4699] 
ThreadContext constructor is not thread-safe, causing loss of submitted tasks.
+- link:https://issues.apache.org/jira/browse/TOMEE-4703[TOMEE-4703] 
ApplicationThreadContextProvider stores a live ThreadContext reference instead 
of an immutable snapshot
+- link:https://issues.apache.org/jira/browse/TOMEE-4704[TOMEE-4704] 
CUTask.invoke() does not safely propagate errors to ManagedTask
+- link:https://issues.apache.org/jira/browse/TOMEE-4708[TOMEE-4708] OpenID 
definition EL expressions are evaluated on a shared ELProcessor and fail under 
concurrent requests (regression of TOMEE-4595)
+- link:https://issues.apache.org/jira/browse/TOMEE-4711[TOMEE-4711] Jakarta 
Data repositories fail when called from a @Transactional CDI method
+- link:https://issues.apache.org/jira/browse/TOMEE-4712[TOMEE-4712] MDB 
endpoints are activated before the application's other EJBs are started
+- link:https://issues.apache.org/jira/browse/TOMEE-4714[TOMEE-4714] 
TomEEEmbeddedExtension (JUnit 5) can not start the container again after it was 
closed
+- link:https://issues.apache.org/jira/browse/TOMEE-4715[TOMEE-4715] TomEE 
embedded application runner does not inject @Resource into the @Application 
descriptor
+- link:https://issues.apache.org/jira/browse/TOMEE-4716[TOMEE-4716] 
MicroProfile Health endpoints are not deployed when the webapp declares a 
JAX-RS Application subclass
+- link:https://issues.apache.org/jira/browse/TOMEE-4727[TOMEE-4727] Jakarta 
Data repository fails when called from an AFTER_SUCCESS transactional observer
+- link:https://issues.apache.org/jira/browse/TOMEE-4728[TOMEE-4728] 
MicroProfile Health endpoint runs the providers of a declared JAX-RS application
+- link:https://issues.apache.org/jira/browse/TOMEE-4729[TOMEE-4729] MP-JWT 
security state is not restored for asynchronous requests
+- link:https://issues.apache.org/jira/browse/TOMEE-4730[TOMEE-4730] MP-JWT 
ignores class-level security annotations of a resource superclass
+- link:https://issues.apache.org/jira/browse/TOMEE-4731[TOMEE-4731] 
TxThreadContextRestorer fails with NPE when managed threads end after the 
container shut down
+
+== Improvement
+
+[.compact]
+- link:https://issues.apache.org/jira/browse/TOMEE-1619[TOMEE-1619] Add 
exception message to Alerts
+- link:https://issues.apache.org/jira/browse/TOMEE-3234[TOMEE-3234] Update 
Examples to use Server / API Boms
+- link:https://issues.apache.org/jira/browse/TOMEE-4662[TOMEE-4662] Speed up 
annotation processing during WAR deploy
+- link:https://issues.apache.org/jira/browse/TOMEE-4709[TOMEE-4709] Track git 
revision in version info
+- link:https://issues.apache.org/jira/browse/TOMEE-4710[TOMEE-4710] Don't 
patch catalina.jar just to print TomEE Version
+
+== Task
+
+[.compact]
+- link:https://issues.apache.org/jira/browse/TOMEE-2850[TOMEE-2850] 
Investigate and remove -j parameter from TCK setup
+- link:https://issues.apache.org/jira/browse/TOMEE-4259[TOMEE-4259] Fix 
"cdi-tck" after OWB-4 upgrade (CDI 4.0)
+- link:https://issues.apache.org/jira/browse/TOMEE-4260[TOMEE-4260] Fix 
"cdi-tck-embedded" after OWB-4 upgrade (CDI 4.0)
+- link:https://issues.apache.org/jira/browse/TOMEE-4634[TOMEE-4634] Remove 
tomee-webaccess
+- link:https://issues.apache.org/jira/browse/TOMEE-4675[TOMEE-4675] update to 
xbean-5.0.0 and owb-4.1.1
+- link:https://issues.apache.org/jira/browse/TOMEE-4700[TOMEE-4700] Drop 
openejb-hessian
+- link:https://issues.apache.org/jira/browse/TOMEE-4701[TOMEE-4701] Drop 
openejb-ssh
+- link:https://issues.apache.org/jira/browse/TOMEE-4702[TOMEE-4702] Drop 
openejb-common-cli
+- link:https://issues.apache.org/jira/browse/TOMEE-4705[TOMEE-4705] Migrate 
the Maven plugins off the Maven 2 API
+- link:https://issues.apache.org/jira/browse/TOMEE-4706[TOMEE-4706] Migrate 
the Gradle plugin to a current Gradle version
+- link:https://issues.apache.org/jira/browse/TOMEE-4707[TOMEE-4707] Drop the 
standalone HTTP server from openejb-http
+- link:https://issues.apache.org/jira/browse/TOMEE-4733[TOMEE-4733] Pin 
Surefire to 3.5.x in TCK modules
+
+== Documentation
+
+[.compact]
+- link:https://issues.apache.org/jira/browse/TOMEE-3738[TOMEE-3738] Replace 
Hibernate Validator with BVal for "Bean Validation TCK"
+- link:https://issues.apache.org/jira/browse/TOMEE-4673[TOMEE-4673] Remove 
"About the 'tomee' webapp" since Tomee drop-in webapp was removed in TOMEE-3724
+
+== Dependency upgrade
+
+[.compact]
+- link:https://issues.apache.org/jira/browse/TOMEE-4687[TOMEE-4687] 
actions/setup-java 6.0.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4630[TOMEE-4630] ActiveMQ 
6.2.7
+- link:https://issues.apache.org/jira/browse/TOMEE-4665[TOMEE-4665] Apache 
ActiveMQ 6.3.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4690[TOMEE-4690] Apache 
ActiveMQ 6.3.3
+- link:https://issues.apache.org/jira/browse/TOMEE-4692[TOMEE-4692] Apache 
BVal 3.1.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4680[TOMEE-4680] Apache CXF 
- CVE-2026-54225 in TomEE 10.2.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4664[TOMEE-4664] Apache 
Neethi 3.2.3
+- link:https://issues.apache.org/jira/browse/TOMEE-4724[TOMEE-4724] Apache 
Neethi 3.2.4
+- link:https://issues.apache.org/jira/browse/TOMEE-4672[TOMEE-4672] 
Bouncycastle 1.86
+- link:https://issues.apache.org/jira/browse/TOMEE-4627[TOMEE-4627] Commons 
Logging 1.4.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4669[TOMEE-4669] 
commons-codec 1.23.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4726[TOMEE-4726] 
commons-lang3 3.21.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4625[TOMEE-4625] CXF 4.2.2
+- link:https://issues.apache.org/jira/browse/TOMEE-4689[TOMEE-4689] CXF 4.2.4
+- link:https://issues.apache.org/jira/browse/TOMEE-4632[TOMEE-4632] 
Eclipselink 5.0.2
+- link:https://issues.apache.org/jira/browse/TOMEE-4663[TOMEE-4663] Geronimo 
Mail 1.1.1
+- link:https://issues.apache.org/jira/browse/TOMEE-4623[TOMEE-4623] Jackson 
2.22.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4667[TOMEE-4667] Jackson 
2.22.1
+- link:https://issues.apache.org/jira/browse/TOMEE-4683[TOMEE-4683] Jackson 
2.22.2
+- link:https://issues.apache.org/jira/browse/TOMEE-4723[TOMEE-4723] Jackson 
2.22.4
+- link:https://issues.apache.org/jira/browse/TOMEE-4684[TOMEE-4684] Johnzon 
2.2.0
+- link:https://issues.apache.org/jira/browse/TOMEE-4719[TOMEE-4719] Jose4j 
0.9.7
+- link:https://issues.apache.org/jira/browse/TOMEE-4685[TOMEE-4685] JUnit 6.1.3
+- link:https://issues.apache.org/jira/browse/TOMEE-4670[TOMEE-4670] Mojarra 
4.1.11
+- link:https://issues.apache.org/jira/browse/TOMEE-4691[TOMEE-4691] Mojarra 
4.1.19
+- link:https://issues.apache.org/jira/browse/TOMEE-4717[TOMEE-4717] MyFaces 
4.1.4
+- link:https://issues.apache.org/jira/browse/TOMEE-4693[TOMEE-4693] Plexus 
Classworlds 2.12.1
+- link:https://issues.apache.org/jira/browse/TOMEE-4629[TOMEE-4629] saaj-impl 
3.0.6
+- link:https://issues.apache.org/jira/browse/TOMEE-4722[TOMEE-4722] SLF4J 
2.0.20
+- link:https://issues.apache.org/jira/browse/TOMEE-4668[TOMEE-4668] SmallRye 
Config 3.18.1
+- link:https://issues.apache.org/jira/browse/TOMEE-4686[TOMEE-4686] SmallRye 
Config 3.18.2
+- link:https://issues.apache.org/jira/browse/TOMEE-4628[TOMEE-4628] Smallrye 
OpenTelemtry 2.15.1
+- link:https://issues.apache.org/jira/browse/TOMEE-4720[TOMEE-4720] Snakeyaml 
2.7
+- link:https://issues.apache.org/jira/browse/TOMEE-4624[TOMEE-4624] Tomcat 
11.0.24
+- link:https://issues.apache.org/jira/browse/TOMEE-4688[TOMEE-4688] Tomcat 
11.0.27
+- link:https://issues.apache.org/jira/browse/TOMEE-4725[TOMEE-4725] WSS4J 4.0.2
+- link:https://issues.apache.org/jira/browse/TOMEE-4633[TOMEE-4633] XBean 4.31
+
diff --git a/src/main/jbake/content/download-archive.adoc 
b/src/main/jbake/content/download-archive.adoc
index 3b0e091..20b6baf 100644
--- a/src/main/jbake/content/download-archive.adoc
+++ b/src/main/jbake/content/download-archive.adoc
@@ -34,9 +34,37 @@ and appreciated.
 
 === Download Links
 
-IMPORTANT: Note: Please note the 10.0.0-M releases are milestone releases 
intended for evaluation purposes and should not be used in production.
+IMPORTANT: Note: Please note the 10.0.0-M and 11.0.0-M releases are milestone 
releases intended for evaluation purposes and should not be used in production.
 
 
+[cols="2,4*^1",options="header"]
+|===
+|Name|Version|Date|Size|Signatures & Hashes
+|https://archive.apache.org/dist/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.zip[icon:download[]
 TomEE Microprofile ZIP] |11.0.0-M1|11 June 2026|70 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.zip.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.tar.gz[icon:download[]
 TomEE Microprofile TAR.GZ] |11.0.0-M1|11 June 2026|70 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.tar.gz.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.zip[icon:download[]
 TomEE Plume ZIP] |11.0.0-M1|11 June 2026|82 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.zip.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.tar.gz[icon:download[]
 TomEE Plume TAR.GZ] |11.0.0-M1|11 June 2026|82 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.tar.gz.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.zip[icon:download[]
 TomEE Plus ZIP] |11.0.0-M1|11 June 2026|74 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.zip.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.tar.gz[icon:download[]
 TomEE Plus TAR.GZ] |11.0.0-M1|11 June 2026|74 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.tar.gz.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.zip[icon:download[]
 TomEE Webprofile ZIP] |11.0.0-M1|11 June 2026|60 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.zip.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.tar.gz[icon:download[]
 TomEE Webprofile TAR.GZ] |11.0.0-M1|11 June 2026|60 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.tar.gz.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-11.0.0-M1/tomee-project-11.0.0-M1-source-release.zip[icon:download[]
 TomEE Project Source Release ZIP] |11.0.0-M1|11 June 2026|22 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/tomee-project-11.0.0-M1-source-release.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/tomee-project-11.0.0-M1-source-release.zip.sha512[icon:download[]
 SHA512]
+|===
+
+[cols="2,4*^1",options="header"]
+|===
+|Name|Version|Date|Size|Signatures & Hashes
+|https://archive.apache.org/dist/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.zip[icon:download[]
 TomEE Microprofile ZIP] |10.2.0|17 July 2026|71 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.zip.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.tar.gz[icon:download[]
 TomEE Microprofile TAR.GZ] |10.2.0|17 July 2026|71 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.tar.gz.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.zip[icon:download[]
 TomEE Plume ZIP] |10.2.0|17 July 2026|83 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.zip.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.tar.gz[icon:download[]
 TomEE Plume TAR.GZ] |10.2.0|17 July 2026|83 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.tar.gz.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.zip[icon:download[]
 TomEE Plus ZIP] |10.2.0|17 July 2026|76 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.zip.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.tar.gz[icon:download[]
 TomEE Plus TAR.GZ] |10.2.0|17 July 2026|75 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.tar.gz.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.zip[icon:download[]
 TomEE Webprofile ZIP] |10.2.0|17 July 2026|61 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.zip.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.tar.gz[icon:download[]
 TomEE Webprofile TAR.GZ] |10.2.0|17 July 2026|61 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.tar.gz.sha512[icon:download[]
 SHA512]
+|https://archive.apache.org/dist/tomee/tomee-10.2.0/tomee-project-10.2.0-source-release.zip[icon:download[]
 TomEE Project Source Release ZIP] |10.2.0|17 July 2026|22 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/tomee-project-10.2.0-source-release.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/tomee-project-10.2.0-source-release.zip.sha512[icon:download[]
 SHA512]
+|===
+
 [cols="2,4*^1",options="header"]
 |===
 |Name|Version|Date|Size|Signatures & Hashes
diff --git a/src/main/jbake/content/download.adoc 
b/src/main/jbake/content/download.adoc
index c591f1b..01e413a 100755
--- a/src/main/jbake/content/download.adoc
+++ b/src/main/jbake/content/download.adoc
@@ -15,22 +15,23 @@ You **must** 
link:https://www.apache.org/info/verification.html[verify] the inte
 - Jakarta EE 11
 - MicroProfile 7.1
 - Java 17 or higher
-- link:11.0.0-M1/release-notes.html[Release Notes]
+- link:11.0.0-M2/release-notes.html[Release Notes]
+- link:11.0.0-M2/migration-guide.html[Migration Guide]
 
-IMPORTANT: Apache TomEE 11.0.0-M1 is a milestone release intended for 
evaluation purposes and should not be used in production. We do not yet pass 
the full Jakarta EE TCK. Feedback on this release is encouraged.
+IMPORTANT: Apache TomEE 11.0.0-M2 is a milestone release intended for 
evaluation purposes and should not be used in production. We do not yet pass 
the full Jakarta EE TCK. Feedback on this release is encouraged.
 
 [cols="2,4*^1",options="header"]
 |===
 |Name|Version|Date|Size|Signatures & Hashes
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.zip[icon:download[]
 TomEE Microprofile ZIP] |11.0.0-M1|11 June 2026|69 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.zip.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.tar.gz[icon:download[]
 TomEE Microprofile TAR.GZ] |11.0.0-M1|11 June 2026|69 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-microprofile.tar.gz.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.zip[icon:download[]
 TomEE Plume ZIP] |11.0.0-M1|11 June 2026|82 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.zip.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.tar.gz[icon:download[]
 TomEE Plume TAR.GZ] |11.0.0-M1|11 June 2026|81 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plume.tar.gz.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.zip[icon:download[]
 TomEE Plus ZIP] |11.0.0-M1|11 June 2026|74 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.zip.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.tar.gz[icon:download[]
 TomEE Plus TAR.GZ] |11.0.0-M1|11 June 2026|73 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-plus.tar.gz.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.zip[icon:download[]
 TomEE Webprofile ZIP] |11.0.0-M1|11 June 2026|60 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.zip.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.tar.gz[icon:download[]
 TomEE Webprofile TAR.GZ] |11.0.0-M1|11 June 2026|59 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/apache-tomee-11.0.0-M1-webprofile.tar.gz.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M1/tomee-project-11.0.0-M1-source-release.zip[icon:download[]
 TomEE Project Source Release ZIP] |11.0.0-M1|11 June 2026|22 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M1/tomee-project-11.0.0-M1-source-release.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M1/tomee-project-11.0.0-M1-source-release.zip.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-microprofile.zip[icon:download[]
 TomEE Microprofile ZIP] |11.0.0-M2|10 November 2026|70 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-microprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-microprofile.zip.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-microprofile.tar.gz[icon:download[]
 TomEE Microprofile TAR.GZ] |11.0.0-M2|10 November 2026|69 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-microprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-microprofile.tar.gz.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plume.zip[icon:download[]
 TomEE Plume ZIP] |11.0.0-M2|10 November 2026|81 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plume.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plume.zip.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plume.tar.gz[icon:download[]
 TomEE Plume TAR.GZ] |11.0.0-M2|10 November 2026|81 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plume.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plume.tar.gz.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plus.zip[icon:download[]
 TomEE Plus ZIP] |11.0.0-M2|10 November 2026|74 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plus.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plus.zip.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plus.tar.gz[icon:download[]
 TomEE Plus TAR.GZ] |11.0.0-M2|10 November 2026|74 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plus.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-plus.tar.gz.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-webprofile.zip[icon:download[]
 TomEE Webprofile ZIP] |11.0.0-M2|10 November 2026|59 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-webprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-webprofile.zip.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-webprofile.tar.gz[icon:download[]
 TomEE Webprofile TAR.GZ] |11.0.0-M2|10 November 2026|59 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-webprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M2/apache-tomee-11.0.0-M2-webprofile.tar.gz.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-11.0.0-M2/tomee-project-11.0.0-M2-source-release.zip[icon:download[]
 TomEE Project Source Release ZIP] |11.0.0-M2|10 November 2026|16 MiB 
|https://downloads.apache.org/tomee/tomee-11.0.0-M2/tomee-project-11.0.0-M2-source-release.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-11.0.0-M2/tomee-project-11.0.0-M2-source-release.zip.sha512[icon:download[]
 SHA512]
 |===
 
 
@@ -39,22 +40,23 @@ IMPORTANT: Apache TomEE 11.0.0-M1 is a milestone release 
intended for evaluation
 - Jakarta EE 10
 - MicroProfile 6.1
 - Java 17 or higher
-- link:10.2.0/release-notes.html[Release Notes]
+- link:10.3.0/release-notes.html[Release Notes]
+- link:10.3.0/migration-guide.html[Migration Guide]
 
 IMPORTANT: As a community-driven project, Apache TomEE relies on the support 
of contributors like you. With limited resources, we need your help to ensure 
its continued development. 
https://tomee.apache.org/community/contributing/contribution-tips.html[Join us 
today] and contribute your skills, ideas and resources to strengthen the future 
development of Apache TomEE.
 
 [cols="2,4*^1",options="header"]
 |===
 |Name|Version|Date|Size|Signatures & Hashes
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.zip[icon:download[]
 TomEE Microprofile ZIP] |10.2.0|17 July 2026|70 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.zip.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.tar.gz[icon:download[]
 TomEE Microprofile TAR.GZ] |10.2.0|17 July 2026|70 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-microprofile.tar.gz.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.zip[icon:download[]
 TomEE Plume ZIP] |10.2.0|17 July 2026|82 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.zip.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.tar.gz[icon:download[]
 TomEE Plume TAR.GZ] |10.2.0|17 July 2026|82 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plume.tar.gz.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.zip[icon:download[]
 TomEE Plus ZIP] |10.2.0|17 July 2026|74 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.zip.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.tar.gz[icon:download[]
 TomEE Plus TAR.GZ] |10.2.0|17 July 2026|74 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-plus.tar.gz.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.zip[icon:download[]
 TomEE Webprofile ZIP] |10.2.0|17 July 2026|60 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.zip.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.tar.gz[icon:download[]
 TomEE Webprofile TAR.GZ] |10.2.0|17 July 2026|60 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/apache-tomee-10.2.0-webprofile.tar.gz.sha512[icon:download[]
 SHA512]
-|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.2.0/tomee-project-10.2.0-source-release.zip[icon:download[]
 TomEE Project Source Release ZIP] |10.2.0|17 July 2026|22 MiB 
|https://downloads.apache.org/tomee/tomee-10.2.0/tomee-project-10.2.0-source-release.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.2.0/tomee-project-10.2.0-source-release.zip.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.3.0/apache-tomee-10.3.0-microprofile.zip[icon:download[]
 TomEE Microprofile ZIP] |10.3.0|10 November 2026|69 MiB 
|https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-microprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-microprofile.zip.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.3.0/apache-tomee-10.3.0-microprofile.tar.gz[icon:download[]
 TomEE Microprofile TAR.GZ] |10.3.0|10 November 2026|69 MiB 
|https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-microprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-microprofile.tar.gz.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.3.0/apache-tomee-10.3.0-plume.zip[icon:download[]
 TomEE Plume ZIP] |10.3.0|10 November 2026|81 MiB 
|https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-plume.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-plume.zip.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.3.0/apache-tomee-10.3.0-plume.tar.gz[icon:download[]
 TomEE Plume TAR.GZ] |10.3.0|10 November 2026|81 MiB 
|https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-plume.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-plume.tar.gz.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.3.0/apache-tomee-10.3.0-plus.zip[icon:download[]
 TomEE Plus ZIP] |10.3.0|10 November 2026|74 MiB 
|https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-plus.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-plus.zip.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.3.0/apache-tomee-10.3.0-plus.tar.gz[icon:download[]
 TomEE Plus TAR.GZ] |10.3.0|10 November 2026|73 MiB 
|https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-plus.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-plus.tar.gz.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.3.0/apache-tomee-10.3.0-webprofile.zip[icon:download[]
 TomEE Webprofile ZIP] |10.3.0|10 November 2026|59 MiB 
|https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-webprofile.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-webprofile.zip.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.3.0/apache-tomee-10.3.0-webprofile.tar.gz[icon:download[]
 TomEE Webprofile TAR.GZ] |10.3.0|10 November 2026|59 MiB 
|https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-webprofile.tar.gz.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.3.0/apache-tomee-10.3.0-webprofile.tar.gz.sha512[icon:download[]
 SHA512]
+|https://www.apache.org/dyn/closer.cgi/tomee/tomee-10.3.0/tomee-project-10.3.0-source-release.zip[icon:download[]
 TomEE Project Source Release ZIP] |10.3.0|10 November 2026|22 MiB 
|https://downloads.apache.org/tomee/tomee-10.3.0/tomee-project-10.3.0-source-release.zip.asc[icon:download[]
 PGP] 
https://downloads.apache.org/tomee/tomee-10.3.0/tomee-project-10.3.0-source-release.zip.sha512[icon:download[]
 SHA512]
 |===
 
 
diff --git a/src/main/jbake/templates/index.gsp 
b/src/main/jbake/templates/index.gsp
index b7586a9..5ddcb7f 100755
--- a/src/main/jbake/templates/index.gsp
+++ b/src/main/jbake/templates/index.gsp
@@ -66,7 +66,7 @@
                        <div class="col-md-6 d-flex f-column-start 
accented-block accent-violet f-space-between">
                     <div class="block-content">
                         <h5 class="muted">Milestone Release - Jakarta EE 
11</h5>
-                        <h4 class="muted">apache-tomee-11.0.0-M1</h4>
+                        <h4 class="muted">apache-tomee-11.0.0-M2</h4>
                         <p>Milestone Release, Apache TomEE 11 implements 
Jakarta EE 11 with MicroProfile 7.1. It runs on Java 17 or higher. Intended for 
evaluation only - not for production.</p>
                     </div>
                     <a class="btn btn-accent btn-primary square"  
href="download.html#tomee-11"><i class="icon_plus"></i>Download</a>
@@ -74,8 +74,8 @@
                 <div class="col-md-6 d-flex f-column-end accented-block 
accent-red f-space-between">
                     <div class="block-content">
                         <h5 class="muted">Final Release - Jakarta EE 10</h5>
-                        <h4 class="muted">apache-tomee-10.2.0</h4>
-                        <p>Final Release, Apache TomEE 10.2 implements Jakarta 
EE 10 with MicroProfile 6.1. It runs on Java 17 or higher.</p>
+                        <h4 class="muted">apache-tomee-10.3.0</h4>
+                        <p>Final Release, Apache TomEE 10.3 implements Jakarta 
EE 10 with MicroProfile 6.1. It runs on Java 17 or higher.</p>
                     </div>
                     <a class="btn btn-accent btn-primary square"  
href="download.html#tomee-10"><i class="icon_plus"></i>Download</a>
                                </div>
diff --git a/src/main/resources/ignored.txt b/src/main/resources/ignored.txt
index 96b38cc..5c19053 100644
--- a/src/main/resources/ignored.txt
+++ b/src/main/resources/ignored.txt
@@ -41,6 +41,6 @@ tomee-9.0/es/examples/vaadin-lts-v10-simple.adoc
 tomee-9.0/es/examples/vaadin-lts-v08-simple.adoc
 tomee-7.0/docs/documentation.old.adoc
 # Comma in filename trips JBake's Oven.bake(); upstream filename is from 
tomee.git/docs
-tomee-10.2/docs/functional-testing-with-openejb,-jetty-and-selenium.adoc
+tomee-10.3/docs/functional-testing-with-openejb,-jetty-and-selenium.adoc
 tomee-11.0/docs/functional-testing-with-openejb,-jetty-and-selenium.adoc
 latest/docs/functional-testing-with-openejb,-jetty-and-selenium.adoc

Reply via email to