This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/jetty.version-10.0.17
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git
discard d19d6d44cd Bump jetty.version from 10.0.16 to 10.0.17
add 3795320684 AXIS2-6051, add /modules/jaxws/resources dir that was
missed in the previous commit because the filename in META-INF dir was renamed
to jakarta.xml.ws.spi.Provider
add db3f11f539 use the last release of xjc-maven-plugin, not the snapshot
add 9f90722380 add some comments that explains a bit about
jakarta.xml.ws.spi.Provider
add 6deed8a6ef Comment out jaxws-integration in the main pom.xml until we
can get the xjc-maven-plugin to have a runtime dependency on jaxb-xjc
add 84e34910a4 Bump org.mockito:mockito-core from 5.5.0 to 5.6.0
add ca1ce0e045 Bump jetty.version from 10.0.16 to 10.0.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 (d19d6d44cd)
\
N -- N -- N refs/heads/dependabot/maven/jetty.version-10.0.17
(ca1ce0e045)
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.
No new revisions were added by this update.
Summary of changes:
modules/jaxws/pom.xml | 9 +++++++++
.../resources/META-INF/services/jakarta.xml.ws.spi.Provider | 1 +
pom.xml | 2 +-
3 files changed, 11 insertions(+), 1 deletion(-)
create mode 100644
modules/jaxws/resources/META-INF/services/jakarta.xml.ws.spi.Provider
