This still pulls in micrometer 1.0.3
dependencies {
compile('org.springframework.boot:spring-boot-starter')
implementation(platform('org.apache.geode:geode-client-bom:1.10.0'))
implementation('org.apache.geode:geode-core')
implementation('org.apache.geode:geode-cq')
testCompile('org.springframework.boot:spring-boot-starter-test')
testCompile 'junit:junit:4.+'
}
> On Sep 25, 2019, at 12:43 PM, Jacob Barrett <jbarr...@pivotal.io> wrote:
>
> Changing subject…
>
>
> Try
> dependencies {
> implementation(platform(‘org.apache.geode:geode-client-bom:1.10.0’))
> implementation(‘org.apache.geode:geode-core’)
> implementation('org.apache.geode:geode-cq’)
> }
>
> Does that make a difference?
>
>
>> On Sep 25, 2019, at 12:35 PM, Owen Nichols <onich...@pivotal.io> wrote:
>>
>> My build.gradle is pretty simple:
>>
>> repositories {
>> mavenCentral()
>> maven {
>> url
>> 'https://repository.apache.org/content/repositories/orgapachegeode-1059'
>> }
>> }
>>
>> dependencies {
>> compile('org.springframework.boot:spring-boot-starter')
>> compile 'org.apache.geode:geode-core:1.10.0'
>> compile 'org.apache.geode:geode-cq:1.10.0'
>> }
>>
>>
>>> On Sep 25, 2019, at 12:29 PM, Jacob Barrett <jbarr...@pivotal.io> wrote:
>>>
>>>
>>>
>>>> On Sep 25, 2019, at 12:26 PM, Owen Nichols <onich...@pivotal.io> wrote:
>>>>
>>>> ⚠️ to run my spring boot client for above test, I had to manually add
>>>> compile 'io.micrometer:micrometer-core:1.2.0' , otherwise local region
>>>> creation blows up with “java.lang.NoSuchMethodError” due to
>>>> spring-boot-starter pulling in micrometer 1.0.3 by default. This never
>>>> happened with previous versions. Not sure if this is outside Geode’s
>>>> control, but it felt like a poor out-of-the-box experience...
>>>
>>> Is your spring app including geode via maven/gradle dependency management?
>>> This may be pointing to a greater issue with dependency exports in the new
>>> release's POM.
>>>
>>> -Jake
>>>
>>
>
