I would say you have a more fundamental problem, in that you shouldn't
be using the Grizzly dependency if you're deploying to Tomcat. Can
com.sun.jersey:jersey-grizzly2-servlet:jar:1.10:compile be switched to
scope "test"? (Assuming you're using grizzly for testing purposes only?)
Apparently Grizzly itself needs that dependency (makes sense) but not
applications hosting on Grizzly (because Grizzly already includes it per
that dependency).
Glen
On 03/08/2012 05:42 PM, Farrukh Najmi wrote:
> Hi Guys,
>
> Currently the following dependency exists:
>
> +- com.sun.jersey:jersey-grizzly2-servlet:jar:1.10:compile
> | +- org.glassfish:javax.servlet:jar:3.1:compile
>
> When deploying my app with
> com.sun.jersey:jersey-grizzly2-servlet:jar:1.10:compile dependency in
> Tomcat 7 I get an error because servlet.jar should not be in my war.
>
> Should the above dependency be scope provided? Shall I file an issue?
>
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza