You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The easiest way to find compatible versions of Spring Vault dependencies is by relying on the Spring Vault BOM we ship with the compatible versions defined.
5
-
In a Maven project you would declare this dependency in the
6
-
`<dependencyManagement />` section of your `pom.xml`:
The version name follows the following patterns: `$\{version\}` for GA and service releases and `$\{version\}-$\{release\}` for snapshots and milestones. `release` can be one of the following:
29
-
30
-
* `SNAPSHOT` - current snapshots
31
-
* `M1`, `M2` etc. - milestones
32
-
* `RC1`, `RC2` etc. - release candidates
4
+
If you want to use Spring Vault in your project, declare a dependency to the `spring-vault-core` artifact.
33
5
34
6
.Declaring a dependency to Spring Vault
35
7
====
@@ -44,10 +16,13 @@ The version name follows the following patterns: `$\{version\}` for GA and servi
44
16
----
45
17
====
46
18
19
+
The easiest way to find compatible versions of Spring Vault dependencies is by inspecting the properties section of link:https://github.com/spring-projects/spring-vault/blob/main/pom.xml[`spring-vault-parent`].
20
+
We generally recommend upgrading to the latest dependency of Jackson, your HTTP clients and your Cloud provider SDK.
21
+
47
22
[[dependencies.spring-framework]]
48
23
== Spring Framework
49
24
50
25
The current version of Spring Vault requires Spring Framework in version
51
-
{springVersion} or better.
26
+
{springVersion} or newer.
52
27
The modules might also work with an older bugfix version of that minor version.
53
28
However, using the most recent version within that generation is highly recommended.
0 commit comments