Error updating group repository metadata maven

The most powerful feature is able to download the project dependency libraries automatically.

In this tutorials, it provides many step by step examples and explanations on using Apache Maven 2.x.

SKIPPED [INFO] RESTAPI Call Node .................................. SKIPPED [INFO] RESTAPI Call Node - Provider .......................

SKIPPED [INFO] RESTAPI Call Node - Features .......................

After that we will enhance the plugin to do some actual work and add custom metadata to the artifact in the Nexus repository.

We might even have downstream clients of our JAR, WAR, and EAR binary artifacts. First, let’s provide a bearing on the attitude of Gradle. It is not just another Domain Specific Language (DSL) on top of the existing build tooling with which we are already familiar.

Gradle would only be a logical successor to Maven if it offered a very thoughtful path to both migration and integration from the world’s largest open source build system. It is, in fact, a progression of selected ideas of our existing build tools. It would be easy to think of Polyglot Maven as an equivalent to Gradle, but alas, the constraints that apply to Maven apply to Polyglot Maven as well, just sans the angle brackets of XML.

In my case I was looking for a way to improve the Continuous Delivery Pipeline we setup using the Jenkins CI server and the Build Pipeline Plugin in a previous blog series [1].

In particular I wanted to add additional metadata to the deployed artifacts after each successful build step.


Leave a Reply