|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
The problem is that the Gradle JPI plugin sets up the build to use http://repo.jenkins-ci.org/releases/. But the Jenkins Maven Parent POM (org.jenkins-ci.main:pom) uses http://repo.jenkins-ci.org/public/ which contains more artifacts. So the Gradle build does not see many artifacts which are neither in Maven Central nor in the Jenkins releases repo.
Pull request with a fix: https://github.com/jenkinsci/gradle-jpi-plugin/pull/13/files