Hello Stephen,
this is definitely a bug (introduced by jersey-server modifications),
fixing it right now. Will be fixed in 1.7-ea02 (tomorrows promoted build).
Thanks for letting us know.
Regards,
Pavel
On 04/06/2011 01:14 PM, Stephen Souness wrote:
> Hi.
>
> I have just tried updating my application to use Jersey server 1.6 and
> noticed that something was bringing in javax-servlet 3.0 as a
> dependency and including it when I deploy my web application.
>
> From examining the dependency hierarchy it would appear that
> jersey-grizzly2 (which is required for jersey-spring) is the offender.
>
> I would expect such a dependency to be scoped as "provided" in the
> pom.xml to prevent it from being included in a generated war.
>
> Given that I am not intending to deploy onto a servlet 3.0 compatible
> server, should I be concerned at introduction of an apparent
> requirement for Servlet 3.0 functionality?
>
>
> --
> Stephen
>