You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2026/06/16 11:23:15 UTC
(camel) branch chore/spring-ws-exclude-opensaml created (now 7e53e821f62a)
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch chore/spring-ws-exclude-opensaml
in repository https://gitbox.apache.org/repos/asf/camel.git
at 7e53e821f62a chore: camel-spring-ws - exclude transitive opensaml dependencies
This branch includes the following new commits:
new 7e53e821f62a chore: camel-spring-ws - exclude transitive opensaml dependencies
The 1 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.
(camel) 01/01: chore: camel-spring-ws - exclude transitive opensaml dependencies
Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch chore/spring-ws-exclude-opensaml
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 7e53e821f62a03fddb3c3eae3f11931fa6357e79
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Tue Jun 16 13:23:03 2026 +0200
chore: camel-spring-ws - exclude transitive opensaml dependencies
The org.opensaml artifacts pulled in by spring-ws-security are hosted on
a third-party Maven repository (build.shibboleth.net) that has proven
unreliable, causing intermittent CI and build failures. Camel's Spring-WS
component does not use OpenSAML, so exclude the entire org.opensaml group.
Co-Authored-By: Claude <no...@anthropic.com>
Signed-off-by: Claus Ibsen <cl...@gmail.com>
---
components/camel-spring-parent/camel-spring-ws/pom.xml | 4 ++++
.../user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc | 6 ++++++
2 files changed, 10 insertions(+)
diff --git a/components/camel-spring-parent/camel-spring-ws/pom.xml b/components/camel-spring-parent/camel-spring-ws/pom.xml
index 9f99d6ceb20a..d3f7ec111533 100644
--- a/components/camel-spring-parent/camel-spring-ws/pom.xml
+++ b/components/camel-spring-parent/camel-spring-ws/pom.xml
@@ -116,6 +116,10 @@
<groupId>xalan</groupId>
<artifactId>xalan</artifactId>
</exclusion>
+ <exclusion>
+ <groupId>org.opensaml</groupId>
+ <artifactId>*</artifactId>
+ </exclusion>
</exclusions>
</dependency>
<dependency>
diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
index e8faf1620b88..1d28db3c3884 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
@@ -1036,6 +1036,12 @@ that namespace are no longer propagated as `Exchange` headers. Routes that relie
header names from inbound SOAP headers can supply a custom `headerFilterStrategy` (via the new
`headerFilterStrategy` endpoint option) to restore the previous behaviour.
+The transitive `org.opensaml` dependencies pulled in by `spring-ws-security` have been excluded.
+Camel's Spring-WS component does not use OpenSAML, and these artifacts are hosted on a third-party
+Maven repository (`build.shibboleth.net`) that has proven unreliable, causing intermittent CI and
+build failures. If your project depends on OpenSAML for SAML-based WS-Security, you will need to
+add the `org.opensaml` dependencies explicitly.
+
=== camel-lucene
The Exchange header values exposed by `LuceneConstants` have been renamed to follow the standard