[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
jglick created JENKINS-14423 Declare direct deps on all Aether artifacts Issue Type: Bug Assignee: olamy Attachments: x.diff Components: maven Created: 13/Jul/12 2:13 PM Description: I have a project which declares a dependency on org.jenkins-ci.lib:lib-jenkins-maven-embedder. With 3.7 it worked fine. Changing the version to 3.9 makes it not work: NoClassDefFoundError on ConfigUtils, a newer aether-utils class. Turns out that aether-utils 1.11 was being used, via dep from maven-core 3.0.3, whereas 1.13 was really needed for use from aether-connector-wagon. lib-jenkins-maven-embedder declared the correct versions in dependencyManagement, but since this is a jar project, that only affected its own version of Aether, not that of projects depending on it. Suggested patch just makes these simple dependencies. Workaround from client of 3.9 is to explicitly request aether-spi and aether-util in 1.13, though there is still some problem with the version of AbstractHttpClientWagon I am trying to diagnose. Project: Jenkins Priority: Minor Reporter: jglick 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-14423) Declare direct deps on all Aether artifacts
olamy commented on JENKINS-14423 Declare direct deps on all Aether artifacts I agree it was a issue to have such declaration and I have applied you patch. Thanks! BTW if your project depends on aether declare those dependencies. Never rely on transitive dependencies !!! 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-14423) Declare direct deps on all Aether artifacts
SCM/JIRA link daemon commented on JENKINS-14423 Declare direct deps on all Aether artifacts Code changed in jenkins User: olivier lamy Path: pom.xml http://jenkins-ci.org/commit/lib-jenkins-maven-embedder/82b63f7cd7e8841993fd8ec452ad4894a5334ed9 Log: JENKINS-14423 Declare direct deps on all Aether artifacts Submiited by Jesse Glick. 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-14423) Declare direct deps on all Aether artifacts
jglick commented on JENKINS-14423 Declare direct deps on all Aether artifacts Client must also apparently depend on wagon-provider-api:org.apache.maven.wagon:2.2 to get AbstractWagon.getTimeout, though I am still unclear on why. 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-14423) Declare direct deps on all Aether artifacts
jglick commented on JENKINS-14423 Declare direct deps on all Aether artifacts The project does not explicitly depend on Aether; just calls MavenEmbedder.buildProjects. 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-14423) Declare direct deps on all Aether artifacts
olamy commented on JENKINS-14423 Declare direct deps on all Aether artifacts Maybe aether read this property ? 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-14423) Declare direct deps on all Aether artifacts
olamy commented on JENKINS-14423 Declare direct deps on all Aether artifacts Do you need a release ? As I will be on holidays this evening for 2 weeks and limited network, I can do it now but not tomorrow BTW feel free to release it. 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-14423) Declare direct deps on all Aether artifacts
jglick edited a comment on JENKINS-14423 Declare direct deps on all Aether artifacts Client must also apparently depend on org.apache.maven.wagon:wagon-provider-api:2.2 to get AbstractWagon.getTimeout, though I am still unclear on why. 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-14423) Declare direct deps on all Aether artifacts
jglick
commented on JENKINS-14423
Declare direct deps on all Aether artifacts
Thanks but I do not think I need a release; explicit deps from client project work fine for now. I would anyway first want to figure out what was going on with AbstractWagon.getTimeout - trying to use 2.1 (the default by transitivity) throws {{NoSuchMethodError}}s.
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-14423) Declare direct deps on all Aether artifacts
jglick edited a comment on JENKINS-14423 Declare direct deps on all Aether artifacts Thanks but I do not think I need a release; explicit deps from client project work fine for now. I would anyway first want to figure out what was going on with AbstractWagon.getTimeout - trying to use 2.1 (the default by transitivity) throws NoSuchMethodError. 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-14423) Declare direct deps on all Aether artifacts
jglick commented on JENKINS-14423 Declare direct deps on all Aether artifacts Oh, looks like you already updated wagonVersion in 3.10-SNAPSHOT, so the problem I had was probably limited to 3.9. 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-14423) Declare direct deps on all Aether artifacts
dogfood commented on JENKINS-14423 Declare direct deps on all Aether artifacts Integrated in lib-jenkins-maven-embedder #33 JENKINS-14423 Declare direct deps on all Aether artifacts (Revision 82b63f7cd7e8841993fd8ec452ad4894a5334ed9) Result = SUCCESS Olivier Lamy : Files : pom.xml 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
