Open MartinWahnschaffe opened 5 years ago
I would like to suggest an alternative: It may be worth looking at migrating the project to Gradle instead of sticking with Maven and Ant. In my point of view, its featureset combines many good features of both Maven and Ant:
dependencyManagement
blocks can be achieved by using io.spring.dependency-management
plugin)Additional advantages from using Gradle as the build system:
build.gradle
files can also include (or reference) arbitrary Groovy and Java code for implementation of custom functionalitysormas-app
project that also uses Gradle
in the Maven scriptsIt seems that resolver-ant-tasks
could avoid the M2_HOME with overwrite mechanism for settings.xml file.
Maven 3.5 no longer gives the instruction to setup the M2_HOME variable, because it is related to several bugs/problems (see https://maven.apache.org/docs/3.5.0/release-notes.html). Our ant scripts rely on this and thus should better be replaced with maven goals (at least to collect server libs, etc.). In addition the maven-ant-tasks plugin for ant is retired (see http://maven.apache.org/ant-tasks/), it has been superseded by Maven Artifact Resolver Ant Tasks.