Hi Jon,
That is because grizzly-webserver is a bundle package that means that is has
packaged all it's dependencies within.
So it should be enough to add only grizzly-webserver into classpath to get
everything you need from grizzly :)
HTH,
Hubert.
On Tue, Nov 17, 2009 at 6:49 PM, Jonathan Gold <jgold.bg_at_gmail.com> wrote:
> Hi --
>
> I've searched through the users@ and dev@ lists, but couldn't seem to find
> any
> answers, so here goes.
>
> I'm building an application that uses the GrizzlyWebServer class to embed
> grizzly, and using maven for the project. Before maven, I used
> grizzly-webserver-1.9.18-e.jar, so I figured that's what I should stick
> with in
> the maven version, putting this in my pom:
>
> <dependency>
> <groupId>com.sun.grizzly</groupId>
> <artifactId>grizzly-webserver</artifactId>
> <version>1.9.18-e</version>
> </dependency>
>
> using the dev.java.net repo. Everything compiles and works fine, but what
> I'm
> noticing is that the classpath that maven assembles (via maven's dependency
> plugin dependency:build-classpath) includes the webserver jar
> as well as redundant jars:
>
>
> .../.m2/repository/com/sun/grizzly/grizzly-comet/1.9.18-e/grizzly-comet-1.9.18-e.jar
>
> .../.m2/repository/com/sun/grizzly/grizzly-cometd/1.9.18-e/grizzly-cometd-1.9.18-e.jar
>
> .../.m2/repository/com/sun/grizzly/grizzly-framework/1.9.18-e/grizzly-framework-1.9.18-e.jar
>
> .../.m2/repository/com/sun/grizzly/grizzly-http/1.9.18-e/grizzly-http-1.9.18-e.jar
>
> .../.m2/repository/com/sun/grizzly/grizzly-http-servlet/1.9.18-e/grizzly-http-servlet-1.9.18-e.jar
>
> .../.m2/repository/com/sun/grizzly/grizzly-portunif/1.9.18-e/grizzly-portunif-1.9.18-e.jar
>
> .../.m2/repository/com/sun/grizzly/grizzly-rcm/1.9.18-e/grizzly-rcm-1.9.18-e.jar
>
> .../.m2/repository/com/sun/grizzly/grizzly-utils/1.9.18-e/grizzly-utils-1.9.18-e.jar
>
> .../.m2/repository/com/sun/grizzly/grizzly-webserver/1.9.18-e/grizzly-webserver-1.9.18-e.jar
> .../.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar
>
> Am I doing something wrong here? I realize the duplicate jars are okay
> since no
> matter which jar a class is loaded from, it's coming from the same grizzly
> build. Still, it makes me uncomfortable having duplication, so wonder if
> some
> experienced maven or grizzly peeps can give me some input?
>
> jon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>