SeleniumHQ / selenium-google-code-issue-archive

Archive, please see main selenium repo
https://github.com/seleniumhq/selenium
345 stars 195 forks source link

Document all maven maven driver dependencies #8327

Closed lukeis closed 8 years ago

lukeis commented 8 years ago

Originally reported on Google Code with ID 8327


**Note1:** I am not sure if this is the correct repository to create this issue, if
it is not please point me to the correct resource.  
**Note 2:** I am a total newbie in using selenium. This is the first time I get my
hands into the docs so I will be creating issues regarding anything that I think should
be documented for clarity.

In `http://docs.seleniumhq.org/docs/03_webdriver.jsp#chapter03-reference`, more specifically
in the "Java" section, there is some dependencies examples in maven:

The below example is pretty intuitive. It is supposed to work as the main dependency
for java.

```xml
<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium-java</artifactId>
  <version>2.44.0</version>
</dependency>

The next dependency though is also pretty clear. It means you should add some kind of "driver" dependency for each browser.

<dependency>
  <groupId>com.opera</groupId>
   <artifactId>operadriver</artifactId>
</dependency>

The problem is that it should contain not only one example of a driver, but the reference to all supported driver artifacts groupIds and artifactIds. This page is supposed to be the first resource to be viewed by a developer after all.

Why is that? You may be asking.

Well, I could look on maven central for "com.google" groupId and "chromedriver" artifactId, but it wouldnt mean I would get the correct and supported artifact. There are cases where people uploaded artifacts using a package but that wasn't the official version of that artifact, that is why the official docs should mention every supported driver, and if it is already mentioned somewhere, it should mention in this specific section to make it clear which drivers are supported.

If the artifacts are mentioned elsewhere: Put the relevant links on this page. If the artifacts are not mentioned elsewhere: Create the artifacts references page and put the relevant links on this page.

I hope this is useful to help the documentation to become better.

(Last note: I am creating an issue instead of a pull request because I believe I don't have enough context of the overall documentation to be able to enhance it in a proper way).


After reading through I realized not all drivers can be used with maven. Chrome, for instance, should be downloaded directly from the website.

This should be referenced early, probably with a link of how to use each driver at http://docs.seleniumhq.org/docs/03_webdriver.jsp#driver-specifics-and-tradeoffs.

Ref: https://github.com/SeleniumHQ/selenium-docs/issues/64


Reported by `admin@fagnermartins.com` on 2014-12-26 17:34:48
lukeis commented 8 years ago

Reported by barancev on 2015-03-08 21:58:41

lukeis commented 8 years ago
that maven reference to operadriver has sense been removed. All the drivers are shown
on the Downloads page.

It's very difficult to have so much information to need to provide and yet provide
concise information for what a particular user needs. I think we probably need new
quick-start guides, for each browser and for each language.

I've logged new issues in github to track this:
https://github.com/SeleniumHQ/docs/issues/69
https://github.com/SeleniumHQ/www.seleniumhq.org/issues/24

Reported by luke.semerau on 2015-04-12 05:17:26

lukeis commented 8 years ago
Now I took a look and found it: 

"If you're using Maven, you will find all Selenium Maven artifacts directly in the
central Maven repository here: http://repo1.maven.org/maven2/org/seleniumhq/selenium/"

Probably it wasn't there at the time this issue was created.

Reported by admin@fagnermartins.com on 2015-04-12 08:41:57

lukeis commented 8 years ago

Reported by luke.semerau on 2015-09-17 18:25:05