SpringBoot Dependency management for ojdbc8-observability refers to a BOM that does not exist on Maven Central

The following dependency in Spring Boot 2.4.0

     <dependency>
        <groupId>com.oracle.database.jdbc</groupId>
        <artifactId>ojdbc-bom</artifactId>
        <version>19.8.0.0</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>

has the transitive dependency to the pom com.oracle.database.observability:ojdbc-bom:pom:19.8.0.0 via com.oracle.database.observability:ojdbc8-observability:19.8.0.0 which is not available in maven central repository yet.

And hence the build for the application using this dependency via Spring Boot 2.4.0 fails with the below error:

Failed to collect dependencies at com.oracle.database.observability:ojdbc8-observability:pom:19.8.0.0: Failed to read artifact descriptor for com.oracle.database.observability:ojdbc8-observability:pom:19.8.0.0: Could not find artifact com.oracle.database.observability:ojdbc-bom:pom:19.8.0.0

Comment From: snicoll

Thanks for the report but, unfortunately, there is nothing we can do about this bom that isn't under our control. The com.oracle.database.observability:ojdbc8-observability:19.8.0.0 bom has a dependency management import for com.oracle.database.observability:ojdbc-bom:19.8.0.0. I wonder if that's a typo? If it is, there is an import cycle between those BOMS which is not ideal either

@Kuassim can you please help us raise that issue at the appropriate place?

Comment From: Sachpat

com.oracle.database.observability:ojdbc8-observability:19.8.0.0 bom has a dependency management import for com.oracle.database.observability:ojdbc-bom:19.8.0.0. I wonder if that's a typo? If it is, there is an import cycle between those BOMS which is not ideal either

That's true. Something definitely is wrong with this dependency management import.

Comment From: Kuassim

Sorry for the inconvenience; we are looking into this, as we speak. Will report back ASAP.

Comment From: Kuassim

We found and fixed the problem however our filer (the person) is on vacation. Hopefully the change will be reflected early next week.

Comment From: Sachpat

We found and fixed the problem however our filer (the person) is on vacation. Hopefully the change will be reflected early next week.

Thanks for the quick fix @Kuassim . Sure, will wait for the change to be reflected.

Comment From: snicoll

Thanks a lot for the quick turnaround @Kuassim. Do I understand the missing BOM is going to be published and nothing on our end is required?

Comment From: Kuassim

That's right @snicoll.

Comment From: snicoll

Thanks for the follow-up. I am going to close this now.