Closed ldez closed 9 years ago
You are right, this is the content of latest Maven BOM file
Which is strange, since when I do the following:
> gradlew clean build -x test
> gradlew install
I got the right file in my local repo. I will upload a snapshot today to maven central repo to see what is going on.
All version of your BOM on Maven Central have the same problem. Why you build a jar ? You should publish only a POM.
Yes, I realized that now :( When I build everything locally, the BOM POM is complete. I assumed this will work when I publish artifacts, too...
And for jar: we are using gradle for building everything and generating POMs. There is an issue with gradle (GRADLE-2427) that required BOM module to be java module - hence we have an empty jar there. I see now there is a new plugin: maven-publish
that should work better.
I will check what is going on and resolve this ;)
Figured out - the BOM data was set only in install
task, but not in the uploadArchives
.
Just uploaded the snapshot; BOM seems ok now:
Well done. Your link works but doesn't appear in Nexus browser (see capture)
Maybe this is because this is just a snapshot repo? afaik, when we do next full release to central maven repo, everything should be ok. And it should be ok when using snapshot dependency in your maven, i guess ;)
The generated pom for BOM doesn't have
dependencyManagement
anddependencies
descriptor.