Yes, created OAK-2827 to track this. On Tue, May 5, 2015 at 10:10 AM, Chetan Mehrotra <[email protected]> wrote:
> Looking at dependency tree it appears that > com.amazonaws:aws-java-sdk-core:jar:1.9.11 has a version range > dependency on joda-time [2.2,) which at times causes issue. We can > possibly try to exclude that dependency from aws-java-sdk and add an > explicit dependency on joda-time with definite version range > > @Amit - Can we try that? > > [ERROR] 1) org.apache.jackrabbit:oak-blob-cloud:bundle:1.4-SNAPSHOT > [ERROR] 2) com.amazonaws:aws-java-sdk:jar:1.9.11 > [ERROR] 3) com.amazonaws:aws-java-sdk-support:jar:1.9.11 > [ERROR] 4) com.amazonaws:aws-java-sdk-core:jar:1.9.11 > > [1] > https://repo1.maven.org/maven2/com/amazonaws/aws-java-sdk-core/1.9.11/aws-java-sdk-core-1.9.11.pom > > Chetan Mehrotra > > > On Mon, May 4, 2015 at 2:22 PM, Michael Dürig <[email protected]> wrote: > > > > Hi, > > > > I've seen this happen a few times lately but with no apparent pattern. > > Anyone has an idea what could be causing this? > > > > Michael > > > > > > On 4.5.15 9:58 , Apache Jenkins Server wrote: > >> > >> [ERROR] Failed to execute goal > >> org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process > (default) > >> on project oak-blob-cloud: Failed to resolve dependencies for one or > more > >> projects in the reactor. Reason: No versions are present in the > repository > >> for the artifact with a range [2.2,) > >> [ERROR] joda-time:joda-time:jar:null > >> [ERROR] > >> [ERROR] from the specified remote repositories: > >> [ERROR] Nexus (http://repository.apache.org/snapshots, releases=false, > >> snapshots=true), > >> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, > >> snapshots=false) > >> [ERROR] Path to dependency: > >> [ERROR] 1) org.apache.jackrabbit:oak-blob-cloud:bundle:1.4-SNAPSHOT > >> [ERROR] 2) com.amazonaws:aws-java-sdk:jar:1.9.11 > >> [ERROR] 3) com.amazonaws:aws-java-sdk-support:jar:1.9.11 > >> [ERROR] 4) com.amazonaws:aws-java-sdk-core:jar:1.9.11 > >> [ERROR] -> [Help 1] > >> [ERROR] > >> [ERROR] To see the full stack trace of the errors, re-run Maven with the > >> -e switch. > >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. > >> [ERROR] > >> [ERROR] For more information about the errors and possible solutions, > >> please read the following articles: > >> [ERROR] [Help > >> 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > >> [ERROR] > >> [ERROR] After correcting the problems, you can resume the build with the > >> command > >> [ERROR] mvn <goals> -rf :oak-blob-cloud >
