easy-cli | a simple CLI for scaffolding of FE | Command Line Interface library

The problem is the jersey-client dependency. You need to remove it. Reason: The generic ClientBuilder is built to always become a JerseyClientBuilder when Jersey client is on the classpath. The JSON dependency you have (that automatically registers with the RESTEast client) resteasy-jackson2-provider is for RESTEasy. So Jersey client doesn't recognize it. You could manually register the provider with the client and it should work.

Your first mistake is to pass an attribute name to find_all(), which interprets the first argument as a tagname instead. Next, you are asking find_all() to filter the tags it finds to only return those that have a a class attribute that matches the given value, tags can't have attribute names with a space in it.

Note that you don't have a class tags here, you have a tags, with a class and href attribute. So you'd want to use

It seems that downgrading to earlier versions like 3.1.0. solved mentioned issue. However, it would be nice not to depend on whole framework just to use client functionalities.

an answer was editing RestService:

IntelliJ was using an old jdk version 1.8 and therefore was also using an older version of JPA (1.0) regardless the dependencies I added. I changed it to the newest jdk version I have installed on my computer and the problem was solved.

have tried changing the version of resteasy-client but it didn't help. during compile time i can see the class, how come at runtime it is missing

Possible reasons could be reasons

1) If you are using maven scope might be provided. so that your jar wont be copied to your distribution.

This is ruled out by above configuration you have mentioned.

2) You are not pointing to correct location from your execution script may be shell script.

3) Your are not passing this jar with --jars option or --driverclasspath --executorclasspath etc...

I doubt issue is because of second or third reasons.

Also have a look at https://spark.apache.org/docs/1.4.1/submitting-applications.html

EDIT :

Question : spark-submit --conf spark.driver.extraClassPath=surfer/javax.ws.rs-api-2.0.1.jar:surfer/jersey-client-2.25.jar:surfer/jersey-common-2.25.jar:surfer/hk2-api-2.5.0-b30.jar:surfer/jersey-guava-2.25.jar:surfer/hk2-utils-2.5.0-b30.jar:surfer/hk2-locator-2.5.0-b30.jar:surfer/javax.annotation-api-1.2.jar artifact.jar againHere.csv

now it throws different exception : Exception in thread "main" java.lang.AbstractMethodError: javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder; i have also tried searching for the class Response$Status$Family somewhere in classpath other than what i am supplying. i used the command grep Response$Status$Family.class /opt/mapr/spark/spark-1.4.1/lib/*.jar And i found that spark also has this class. May be this is the issue. but how to forcefully tell the jvm to use the class supplied by me at runtime and not that of spark, i don't know! can you help?

Since you provided external jar in the classpath

1. through spark submit
2. conf.set...

Since you are using 1.4.1 see configuration options

spark.executor.userClassPathFirst false (Experimental) Same functionality as spark.driver.userClassPathFirst, but applied to executor instances.

spark.driver.userClassPathFirst false (Experimental) Whether to give user-added jars precedence over Spark's own jars when loading classes in the the driver. This feature can be used to mitigate conflicts between Spark's dependencies and user dependencies. It is currently an experimental feature. This is used in cluster mode only. can be used to to tell framework