jenkinsci/gradle-jpi-plugin — pull request #36 by daspilker (2014-12-31 13:23:51+00:00)
Title: Migration to maven-publish plugin

Upcoming changes in Gradle 2.3 ([GRADLE-2999](https://issues.gradle.org/browse/GRADLE-2999)) will allow to publish a second artifact without classifier. This enables the Gradle JPI Plugin to publish the plugin JAR together with the JPI file ([JENKINS-25007](https://issues.jenkins-ci.org/browse/JENKINS-25007)).

Publishing a second artifact is only possible with the maven-publish plugin. This pull requests migrates to the maven-publish plugin.

As a consequence the `install`, `deploy` and `uploadArchives` tasks are no longer available for publishing JPI files and have been replaced by the `publishToMavenLocal` and `publish` tasks.

The generated POM also differs. It no longer contains a reference to the Jenkins plugin parent POM and all dependencies have the runtime scope. That should not matter as long as only the JPI file is published because the POM is only consumed by the [Jenkins Update Center Generator](https://github.com/jenkinsci/backend-update-center2) and the POM contains all relevant information used by the Jenkins Update Center Generator. The POM needs to be adapted when publishing the JAR file.