[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Affects Version/s: 1.14.4 (was: 1.14.3) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Improvement > Components: core >Affects Versions: 1.14.4 >Reporter: John Blum >Priority: Major > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and > major topics is Observability (Metrics and Monitoring, with Tracing, and so > on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Priority: Major (was: Blocker) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Improvement > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Major > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and > major topics is Observability (Metrics and Monitoring, with Tracing, and so > on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Description: As part of the ongoing story and themes in Spring Framework 6, Spring Data 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is Observability (Metrics and Monitoring, with Tracing, and so on). As part of that effort, Micrometer is undergoing a major revision change from 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode no longer runs (or even will build) with Micrometer 2.0. Either Micrometer should be upgraded to 2.0 (most likely in the next major version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, perhaps only enabled when Micrometer is on the classpath. Still a cleaner separation is needed if [Spring] Apache Geode users require and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on Micrometer 1.x (currently [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] in Apache Geode {{1.14.3}}). was: As part of the ongoing story and themes in Spring Framework 6, Spring Data 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is Observability (Monitoring with Metrics, Tracing, and so on). As part of that effort, Micrometer is undergoing a major revision change from 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode no longer runs (or even will build) with Micrometer 2.0. Either Micrometer should be upgraded to 2.0 (most likely in the next major version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, perhaps only enabled when Micrometer is on the classpath. Still a cleaner separation is needed if [Spring] Apache Geode users require and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on Micrometer 1.x (currently [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] in Apache Geode {{1.14.3}}). > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Improvement > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Blocker > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and > major topics is Observability (Metrics and Monitoring, with Tracing, and so > on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Priority: Blocker (was: Major) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Improvement > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Blocker > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and > major topics is Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10045: -- Issue Type: Improvement (was: Bug) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Improvement > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Major > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and > major topics is Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10045: -- Labels: Micrometer (was: Micrometer blocks-1.15.0) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Bug > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Major > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and > major topics is Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10045: -- Parent: (was: GEODE-10003) Issue Type: Bug (was: Sub-task) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Bug > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Major > Labels: Micrometer, blocks-1.15.0 > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and > major topics is Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Priority: Major (was: Blocker) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Sub-task > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Major > Labels: Micrometer, blocks-1.15.0 > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and > major topics is Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-10045: -- Labels: Micrometer blocks-1.15.0 (was: Micrometer) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Sub-task > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Blocker > Labels: Micrometer, blocks-1.15.0 > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and > major topics is Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Description: As part of the ongoing story and themes in Spring Framework 6, Spring Data 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is Observability (Monitoring with Metrics, Tracing, and so on). As part of that effort, Micrometer is undergoing a major revision change from 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode no longer runs (or even will build) with Micrometer 2.0. Either Micrometer should be upgraded to 2.0 (most likely in the next major version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, perhaps only enabled when Micrometer is on the classpath. Still a cleaner separation is needed if [Spring] Apache Geode users require and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on Micrometer 1.x (currently [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] in Apache Geode {{1.14.3}}). was: As part of the ongoing story and themes in Spring Framework 6, Spring Data 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is Observability (Monitoring with Metrics, Tracing, and so on). As part of that effort, Micrometer is undergoing a major revision change from 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode no longer runs (or even will build) with Micrometer 2.0. Either Micrometer should be upgraded to 2.0 (most likely in the next major version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, perhaps only enabled when Micrometer is on the classpath. Still a cleaner separation is needed if [Spring] Apache Geode users require and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on Micrometer 1.x (currently [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] in Apache Geode {{1.14.3}}). > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Sub-task > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Blocker > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and > major topics is Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Priority: Blocker (was: Minor) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Sub-task > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Blocker > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is > Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Priority: Minor (was: Blocker) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Sub-task > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Minor > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is > Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10045: -- Parent: GEODE-10003 Issue Type: Sub-task (was: Improvement) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Sub-task > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Blocker > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is > Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Priority: Blocker (was: Major) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Improvement > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Blocker > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is > Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Component/s: core > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Improvement > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Major > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is > Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Labels: Micrometer (was: ) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Improvement > Components: core >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Major > Labels: Micrometer > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is > Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10045: -- Summary: Upgrade to Micrometer 2.0 (was: Upgrade Apache Geode to Micrometer 2.0) > Upgrade to Micrometer 2.0 > - > > Key: GEODE-10045 > URL: https://issues.apache.org/jira/browse/GEODE-10045 > Project: Geode > Issue Type: Improvement >Affects Versions: 1.14.3 >Reporter: John Blum >Priority: Major > > As part of the ongoing story and themes in Spring Framework 6, Spring Data > 3.0 and the rest of the Spring portfolio, 1 of the new and major topics is > Observability (Monitoring with Metrics, Tracing, and so on). > As part of that effort, Micrometer is undergoing a major revision change from > 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode > no longer runs (or even will build) with Micrometer 2.0. > Either Micrometer should be upgraded to 2.0 (most likely in the next major > version of Geode, i.e. 2.0) or Micrometer should be an optional dependency, > perhaps only enabled when Micrometer is on the classpath. > Still a cleaner separation is needed if [Spring] Apache Geode users require > and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on > Micrometer 1.x (currently > [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231] > in Apache Geode {{1.14.3}}). -- This message was sent by Atlassian Jira (v8.20.1#820001)