SeleniumHQ / SeleniumHQ/htmlunit-driver
Lack of standard naming for standalone server JAR files
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 266
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the release configuration that produces the standalone server JARs and compare the existing artifact names; done means the releases consistently use the established selenium-server-standalone-.jar convention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100