Run mvn dependency:tree and it should be clear where your dependencies come from.
Marek
On 24 Mar 2014, at 21:46, Robert DiFalco <robert.difalco_at_gmail.com> wrote:
> Anyone have any thoughts on this?
>
>
> On Thu, Mar 20, 2014 at 8:36 PM, Robert DiFalco <robert.difalco_at_gmail.com> wrote:
> I can't quite figure out how to get the Jersey Dependencies right.
>
> I am creating a Grizzly-HTTP jersey app. I do use jersey (as well as HK2) features in my code and I also use Bean Validation.
>
> It seems like no matter WHAT I do that client comes in for the compile scope (I know it comes in for test). Is this expected? Maybe it is and I just got confused by the docs.
>
> It seems like jersey-server and jersey-validation will both bring in jersey-client. Correct? Is the idea that you cannot build a server without the client?
>
> Here's what's in my pom.xml.
>
> <dependency>
> <groupId>org.glassfish.grizzly</groupId>
> <artifactId>grizzly-http-server</artifactId>
> <version>${grizzly-http-server.version}</version>
> </dependency>
> <dependency>
> <groupId>org.glassfish.jersey.containers</groupId>
> <artifactId>jersey-container-grizzly2-http</artifactId>
> <version>${jersey.version}</version>
> </dependency>
> <dependency>
> <groupId>org.glassfish.jersey.ext</groupId>
> <artifactId>jersey-bean-validation</artifactId>
> <version>${jersey.version}</version>
> </dependency>
>
>