Hi, On Tue, 10 Jun 2025 at 13:15, Tamás Cservenák <ta...@cservenak.net> wrote: > Where is this POM coming from? > https://central.sonatype.com/artifact/org.netbeans.cluster/platform/overview > > As with simple change (move entries as depMgmt, leave versionless > entries in place) the POM could works a BOM as well, so no need to > "copy paste" but just import and you get aligned with platform
It's generated by the tooling at https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin/blob/master/nb-repository-plugin/src/main/java/org/apache/netbeans/nbm/repository/PopulateRepositoryMojo.java There's a cluster POM for every module cluster - mostly correlated to the top dirs in the repository - https://github.com/apache/netbeans They act as a way to include all the modules of the cluster without having to specify them all individually. The copy paste is a choice to have a controlled list of select modules, rather than the whole cluster - it's useful to copy select groups of modules from there. The other option, I guess, would be exclusions if someone wanted almost everything from a cluster. This tooling is quite old, and a few things could probably do with a rethink. I did start experimenting with a more BOM approach a couple of years back. It would be better in my opinion if we could deploy modules using their specification versions rather than (eg. RELEASE260), then have BOMs that correlate to platform releases. That way we could deliver point updates to modules between releases. We've only done that a couple of times because it requires releasing every module again! Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
