Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lack of standard naming for standalone server JAR files #73

Open
sbabcoc opened this issue Oct 8, 2018 · 0 comments
Open

Lack of standard naming for standalone server JAR files #73

sbabcoc opened this issue Oct 8, 2018 · 0 comments

Comments

@sbabcoc
Copy link

sbabcoc commented Oct 8, 2018

There's a longstanding convention of naming the uber JAR files for Selenium server releases as "selenium-server-standalone-<version>.jar". Initially, this project followed this convention, which enabled parameterized handling of access to these non-Maven artifacts. With the transition to Selenium 3, however, this convention has been abandoned. To make things worse, these releases aren't even consistent with each other... you started out with names that looked like classified artifacts ("with-dependencies"), then altered the classifier ("jar-with-dependencies"). Why not just stick with the established naming convention?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant