[Htmlunit-user] using selenium with 2.14 snapshot

[David M. G. <mic...@gm...>]

Hi all,

I have the following question:

I am using htmlunit through selenium. selenium currently uses htmlunit 2.13.
I want to enjoy from the latest code and the latest fixes, so i want to use
htmlunit 2.14-snapshot.
Do you think it is a good idea, or will i have problems with
incompatibilities between 2.13 and 2.14 snapshot?

If it is a good idea, how do i tell selenium in maven not do download the
dependency of htmlunit so that i can inject the snapshot dependency?


I tried in the meanwhile to get the 2.14 SNAPSHOT through maven but got the
error:

Missing artifact net.sourceforge.htmlunit:htmlunit:jar:2.14-SNAPSHOT

Here is my pom:
project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>htmlunitSandbox</groupId>
  <artifactId>htmlunitSandbox</artifactId>
  <version>0.0.1-SNAPSHOT</version>
   <repositories>
        <repository>
            <snapshots>
                <enabled>true</enabled>
                <updatePolicy>always</updatePolicy>
            </snapshots>
            <releases>
                <enabled>false</enabled>
            </releases>
            <id>sonatype-nexus-snapshots</id>
            <name>Sonatype Nexus Snapshots</name>
            <url>https://oss.sonatype.org/content/repositories/snapshots
</url>
            <layout>default</layout>
        </repository>
    </repositories>
    <dependencies>
    <dependency>
  <groupId>net.sourceforge.htmlunit</groupId>
  <artifactId>htmlunit</artifactId>
  <version>2.14-SNAPSHOT</version>
</dependency>
    </dependencies>
  <build>
    <sourceDirectory>src</sourceDirectory>
    <plugins>
      <plugin>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>3.1</version>
        <configuration>
          <source>1.6</source>
          <target>1.6</target>
        </configuration>
      </plugin>
    </plugins>
  </build>
</project>

Is there anything wrong in this pom?
Thanks,
David