Try the link as update site by pasting it into the "install new software" dialog from Eclipse. Accessing the link from the browser gives you the access denied error.
HTH,
Martin
Try the link as update site by pasting it into the "install new software" dialog from Eclipse. Accessing the link from the browser gives you the access denied error.
HTH,
Martin
Martin Lippert
SpringSource, a division of VMware
SpringSource Tools Team
http://www.springsource.com
http://twitter.com/martinlippert
I"m using Selenium 2. I applied the patch and am still getting this problem.
Here is a pom extract:
When I add xerces as an exclusion:Code:<dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-server</artifactId> <version>2.0rc2</version> <scope>test</scope> <exclusions> <exclusion> <artifactId>commons-logging</artifactId> <groupId>commons-logging</groupId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-remote-control</artifactId> <version>2.0rc2</version> <scope>test</scope> </dependency>
The STS Problems view no longer complains. But at runtime I get a complaint that Xerces is missing.Code:<dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-server</artifactId> <version>2.0rc2</version> <scope>test</scope> <exclusions> <exclusion> <artifactId>commons-logging</artifactId> <groupId>commons-logging</groupId> </exclusion> <exclusion> <artifactId>xercesImpl</artifactId> <groupId>xerces</groupId> </exclusion> </exclusions> </dependency>
java.lang.NoClassDefFoundError: org/apache/xerces/xni/XNIException
(Of course; I excluded it)
OSX 10.5.8
Java 1.5
STS Version: 2.6.1.RELEASE
Sorry, I fixed it myself.
I was on an older backup macbook temporarily and didn't realize that there was a java 1.6 update for Leopard.
http://support.apple.com/kb/DL1359
That fixed it.
The link points to an update site, which can put into the "install new software" dialog of STS/Eclipse. It is not meant to open in a browser.
Also think about using the latest 2.7.0.M2, for which you don't need the patch... :-)
HTH,
Martin
Martin Lippert
SpringSource, a division of VMware
SpringSource Tools Team
http://www.springsource.com
http://twitter.com/martinlippert
I just updated the Eclipse plugin to 2.7.0 RELEASE and am still having similar problem. is the M2 version newer than the RELEASed version?
please disregard. I chose to "validate" the beans again and everything seems to be working as expected. thank you.