This is an automated email from the ASF dual-hosted git repository.
rzo1 pushed a change to branch amq6
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 62765325df Exclude bean validaiton tck tests from
"org.hibernate.beanvalidation.tck.tests.constraints.groups.groupconversion.*"
as they seem to be broken in BVAL itself with Java 17
discard a1c2529891 Upgrade Mockito to make it work under J17+ env
discard ef0b94bc31 Add ScriptEngine implementation for js on Java 15+
discard e1a252419e Merge remote-tracking branch 'jm/amq6-java17' into amq6
discard b2c0a6df1a Adds --add-opens for legacy code fragements with libraries
not supporting J17+
discard e6d427d38f Migrate V11 to V17 class constant in jwt tests
discard 97c5831e8c Fix openejb-hessian tests
discard 815f812cdb mp-jwt generate java 17 class files
discard cf1e2e70a7 Add ScriptEngine implementation for js in
tomee-embedded-maven-plugin as well
discard 392d68b311 Add ScriptEngine implementation for js on Java 15+
discard 8e357423ef Bump maven-plugin-plugin version
discard 1a7ec1c104 Switch Java Level to 17
discard 224f735854 AMQ6 Fileupload 2 Drop related shades
new dd9e594ae7 TOMEE-4317 - ActiveMQ 6.1.0 Drop related shades.
new a84c278189 Switch Java Level to 17
new d10dc48cea Migrate V11 to V17 class constant in jwt tests
new 095765f8af Adds --add-opens for legacy code fragements with libraries
not supporting J17+
new f7daf6cb6b Bump maven-plugin-plugin version
new 71354a23d4 Add ScriptEngine implementation for js on Java 15+
new e082bd53ae Add ScriptEngine implementation for js in
tomee-embedded-maven-plugin as well
new 6cfd850ff0 Add ScriptEngine implementation for js on Java 15+
new 75fc5e7de9 Upgrade Mockito to make it work under J17+ env
new fba5b7bf87 Exclude bean validaiton tck tests from
"org.hibernate.beanvalidation.tck.tests.constraints.groups.groupconversion.*"
as they seem to be broken in BVAL itself with Java 17
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (62765325df)
\
N -- N -- N refs/heads/amq6 (fba5b7bf87)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 10 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
server/openejb-hessian/pom.xml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
