You can test the query in your browser to see the XML results returned by the API.Now we are going to use some simple Groovy to query the API using the HTTP query we just described, extract the results and populate the drop-down.In particular I wanted to add additional metadata to the deployed artifacts after each successful build step.This blog article will guide you through the creation of a Jenkins plugin.This can be useful if there are Maven projects that consume the output of a bnd workspace.
The plugin will print out “Hello World” if you run it during a build step.
This can result in generating source and javadoc jars.
By default, a local only release only installs the actual binary.
I assume you have a working version of Maven installed as well as the Java JDK.
In order to use the maven-hpi-plugin you need to add the following to your Maven that you find under $HOME/.m2/│ └── de │ └── mb │ └── Hello World └── resources ├── de │ └── mb │ └── Hello World Builder │ ├── config.jelly │ ├── global.jelly │ ├── │ └── help-use └── [email protected]:~/workspaces/jenkins/nexus-metadata-plugin$ tree .
That is, the location of a JAR defines if it is released, there is no need to reflect the release status in the version.