You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: