This message was deleted.
# community-support
s
This message was deleted.
m
How are you adding BOMs? If you are interested in the
.xml
files, then the dependencies you add should be with artifact type
@pom
v
I’m using the version catalogue
e.g.
Copy code
dependencies {
    add("boms", libs.gruBom)
}
Copy code
gruBom = {group = "com.agorapulse", name = "gru-bom", version.ref = "gru-version" }
m
this will just add a dependency on the BOM, but it's not a library, so it won't resolve to anything
if you want to resolve the pom files, you need to tell Gradle "I need the POM files"
so should be something like :
Copy code
dependencies {
   add("boms", libs.gruBom) { artifact { type = "pom" } }
}
(untested, just from memory)
v
you’re real hero 🦸
it works
v
I'm curious, may I ask what you plan to do with the BOM content?
v
it might be something something similar as @melix. I would like to add dependencies from the BOM into the version catalog directly
so the consumers can use
Copy code
implementation myCatalog.myLibFromBom
instead of
Copy code
implementation platform(myCatalog.myLibBom)
implementation 'com.example:my-library'
(I haven’t dug deeper in the Micronaut plugin code, but I think it’s doing something similar)
v
I see.
v
it could be nice feature for the next version of the catalog itself 😉