selenium-bom for Maven artifacts?

[psiroky]

Hello,

would it make sense to have org.seleniumhq.selenium:selenium-bom which would define versions (in dependencyMangement) of all Selenium Java artifacts?

There is already a BOM that is being maintained by Arquillian community (https://github.com/arquillian/arquillian-selenium-bom). It needs to be maintained by someone else and it needs to be kept up to date. If it would be directly in Selenium source, it would be automatically available with every new release.

Are there reasons why it was decided not to have such BOM? Or it simply wasn't done yet? (I might have some time to help here...)

[lukeis]

I think just no one has cared to do one. Also, I don't see much point in them, I personally prefer to be more explicit in my poms and define the dependency management section myself and rely on the dependency convergence plugin to make sure things are acting correctly.

I'm not opposed to a Pull Request being made.

[psiroky]

Thanks for quick response @lukeis! I will try to add the BOM and will create PR when I find some spare time.

[joergsesterhenn]

We would also like to use this at our company. If you have to maintain parentpoms for big enterprises BOMs can save you a lot of maintenance time.

The BOM provided by Arquillian could be used as template. I asked them to consider a PR here instead of updating their BOM: arquillian/arquillian-selenium-bom#23

[shs96c]

This will require us to patch https://github.com/bazelbuild/rules_jvm_external to support this functionality.

[github-actions]

This issue is stale because it has been open 280 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[remal]

Please keep it open

[diemol]

Would you like to contribute and work on this @remal?

Otherwise, this has been open for 7 years and there is not a huge interest in it.