|
||||||||
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 |
[JIRA] (JENKINS-13754) Error when compiling a plugin against jenkins version 1.463
scm_issue_l...@java.net (JIRA) Mon, 29 Oct 2012 09:41:47 -0700
- [JIRA] (JENKINS-13754) Error when compiling... ari.hytti...@gmail.com (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... lka...@gmail.com (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... lka...@gmail.com (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... k...@kohsuke.org (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... dogf...@java.net (JIRA)
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
core/pom.xml
maven-plugin/pom.xml
http://jenkins-ci.org/commit/jenkins/abeebce2230c37c1ad6bd6b5d5af615859980568
Log:
[FIXED JENKINS-13754]
while I can't pinpoint what's really causing this, moving this
dependency to core seems to solve the problem.
Guava is defined as dependency in org.kohsuke.stapler:stapler, then
redefined to a newer version in maven-plugin. The latter gets to plugins
as a test scope. When I look at the dependency scope of this in a plugin
project in IntelliJ IDEA, it reports this dependency as the test scope
(and this makes the error somewhat understandable.)