Fixed wrong Spring version

Signed-off-by: Dominic Schabel <dominic.schabel@bosch-si.com>
This commit is contained in:
Dominic Schabel
2019-09-03 17:19:39 +02:00
parent a85dafaad5
commit dba972423b

24
pom.xml
View File

@@ -128,12 +128,12 @@
<properties> <properties>
<java.version>1.8</java.version> <java.version>1.8</java.version>
<spring.boot.version>2.1.3.RELEASE</spring.boot.version> <spring.boot.version>2.1.4.RELEASE</spring.boot.version>
<spring.cloud.version>Greenwich.RELEASE</spring.cloud.version> <spring.cloud.version>Greenwich.RELEASE</spring.cloud.version>
<snapshotDependencyAllowed>true</snapshotDependencyAllowed> <snapshotDependencyAllowed>true</snapshotDependencyAllowed>
<!-- Spring boot version overrides (should be reviewed with every boot <!-- Spring boot version overrides (should be reviewed with every boot
upgrade) - START --> upgrade) - START -->
<!-- Newer versions needed than defined in Boot --> <!-- Newer versions needed than defined in Boot -->
<!-- Fixed dependencies --> <!-- Fixed dependencies -->
@@ -222,8 +222,8 @@
<artifactId>maven-enforcer-plugin</artifactId> <artifactId>maven-enforcer-plugin</artifactId>
<executions> <executions>
<execution> <execution>
<!-- Make sure that only non-snapshot versions are used <!-- Make sure that only non-snapshot versions are used
for the dependencies. Only active when property 'snapshotDependencyAllowed' for the dependencies. Only active when property 'snapshotDependencyAllowed'
is false. --> is false. -->
<id>enforce-no-snapshots</id> <id>enforce-no-snapshots</id>
<goals> <goals>
@@ -480,14 +480,14 @@
<build> <build>
<plugins> <plugins>
<plugin> <plugin>
<!-- Use the Nexus Staging plugin as a full replacement <!-- Use the Nexus Staging plugin as a full replacement
for the standard Maven Deploy plugin. See https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin for the standard Maven Deploy plugin. See https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
why this makes sense :-) We can control whether we want to deploy to the why this makes sense :-) We can control whether we want to deploy to the
Eclipse repo or Maven Central by a combination of the version being a SNAPSHOT Eclipse repo or Maven Central by a combination of the version being a SNAPSHOT
or RELEASE version and property skipNexusStaging=true/false. In any case or RELEASE version and property skipNexusStaging=true/false. In any case
we can take advantage of the plugin's "deferred deploy" feature which makes we can take advantage of the plugin's "deferred deploy" feature which makes
sure that all artifacts of a multi-module project are deployed as a whole sure that all artifacts of a multi-module project are deployed as a whole
at the end of the build process instead of deploying each module's artifacts at the end of the build process instead of deploying each module's artifacts
individually as part of building the module. --> individually as part of building the module. -->
<groupId>org.sonatype.plugins</groupId> <groupId>org.sonatype.plugins</groupId>
<artifactId>nexus-staging-maven-plugin</artifactId> <artifactId>nexus-staging-maven-plugin</artifactId>