geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joao Peixoto (JIRA)" <>
Subject [jira] [Commented] (GEODE-118) Gradle dependencies do not follow repositories transitively
Date Wed, 15 Jul 2015 16:42:05 GMT


Joao Peixoto commented on GEODE-118:

I agree that gradle may be the guilty one here. 

After talking about it with [~GregChase] he advised to still create it since it was an usability
problem, in the sense that a newcomer (such as myself) was having a hard time just bootstrapping
a very basic app, even though the advised dependencies were included.

You may find [~jblum]'s reply here:

> Gradle dependencies do not follow repositories transitively
> -----------------------------------------------------------
>                 Key: GEODE-118
>                 URL:
>             Project: Geode
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: 1.0.0-incubating
>         Environment: Gradle 2.2.1
> OS:           Mac OS X 10.9.5 x86_64
> JVM:          1.8.0_40 (Oracle Corporation 25.40-b25)
>            Reporter: Joao Peixoto
> Using a very basic Gradle setup with dependency on ""
throw an exception:
> "java.lang.ClassNotFoundException: com.gemstone.gemfire.internal.GemFireVersion"
> Note from [~jblum] on the mailing list: if using Gradle, know that Gradle has some bizarre
bug (bug #?) where "repos" are not transitively used to resolve dependencies of dependencies.
This is not an issue for Maven.

This message was sent by Atlassian JIRA

View raw message