Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
selenium-bom for Maven artifacts?
See original GitHub issueHello,
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…)
Issue Analytics
- State:
- Created 8 years ago
- Reactions:6
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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: https://github.com/arquillian/arquillian-selenium-bom/issues/23
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.