<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-remote-control</artifactId>
<version>2.0b3</version>
</dependency>
But this broke when RC2 came out (I didn't update to RC1). It's all a bit
inconsistent atm IMHO as it changed between 2.0b1 and 2.0b2 as well, this is
currently working for me:
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium</artifactId>
<version>2.0rc2</version>
<type>pom</type>
</dependency>
I have no idea what the final is going to look like. Can somebody who does
the maven release explain what the correct way is now (and update the docs
and the wiki so they all say the same thing).
--
You received this message because you are subscribed to the Google Groups
"Selenium Developers" group.
To post to this group, send email to selenium-...@googlegroups.com.
To unsubscribe from this group, send email to
selenium-develo...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/selenium-developers?hl=en.
--
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
If you have received this email in error please notify postm...@ardescosolutions.com
The docs tell us to use:
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-remote-control</artifactId>
<version>...</version>
</dependency>
However this doesn’t work with 2.0rc2, instead we have to use:
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium</artifactId>
<version>2.0rc2</version>
<type>pom</type>
</dependency>
I have tried with:
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-remote-control</artifactId>
<version>2.0rc2</version>
<type>pom</type>
</dependency>
and
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-remote-control</artifactId>
<version>2.0rc2</version>
</dependency>
but it doesn’t work
Kind regards, Michael
2011/6/10 Luke Inman-Semerau <luke.s...@gmail.com>
>> *From:* selenium-...@googlegroups.com [mailto:
>> selenium-...@googlegroups.com] *On Behalf Of *Michael Tamm
>> *Sent:* 09 June 2011 14:07
>> *To:* selenium-...@googlegroups.com
>> *Subject:* Re: [selenium-developers] Re: Selenium2>>Child POM
>> Error>>Missing artifact org.seleniumhq.selenium:selenium:jar:2.0rc2
>>
>>
>>
>> Hi,
>>
>>
>>
>> I have updated the Maven docs weeks ago, but it seems they are hard
>> to
>> find: http://seleniumhq.org/download/maven.html
>>
>>
>>
>> I'm still wondering if I have got the maven artifact names right:
>> Many people fail to recognize, that the selenium artifact has
>> packaging pom. But it only has dependencies to selenium-remote-control
and selenium-server.
>> Maybe we should change the packaging back to jar, but what should go
>> inside that jar? Or should we maybe stop providing the selenium
>> artifact? Does anybody might want to use a selenium-all artifact
>> without dependencies? I have no idea. So please, Maven users out there,
tell me your suggestions=