Apologies for the misplaced post. The issue went away by installing the jersey bundle instead of the particular artifact javax.ws.rs
Also, the verifier indeed was a bit too picky by suggesting the build would fail when it actually was working. Thanks anyway, Dimitris On Tue, Oct 6, 2009 at 11:15 AM, Entner Harald <[email protected]> wrote: > Does the jar reside in the war file? > > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:[email protected]] Im Auftrag von > dtiodtio > Gesendet: Samstag, 3. Oktober 2009 21:49 > An: [email protected] > Betreff: Failed deployment of Maven project to Glassfish > > Hello, > > I recently converted from ant to maven and I'm now trying to deploy to > GlassFish the Maven .war of a multimodule project. The .war file is built > successfully with its dependencies (using the NetBeans IDE) and deployed > using the GlassFish Admin Console (still don't have the hang of deploying > through NetBeans using plugins). However, deployment fails with the given > server.log message (as produced by checking the Verifier flag in the Admin > Console): > > Failed to find following classes: > [ > javax.ws.rs.core.ApplicationConfig > ] > > referenced in the following call stack : > > at com.sun.jersey.api.core.ResourceConfig > at com.sun.jersey.api.core.DefaultResourceConfig > at com.sun.jersey.api.core.ApplicationConfigAdapter > at com.sun.jersey.spi.container.servlet.ServletContainer > > However, I have the following entry > > <dependency> > <groupId>javax.ws.rs</groupId> > <artifactId>jsr311-api</artifactId> > <version>1.1</version> > <scope>compile</scope> > </dependency> > > in the .war pom.xml > > Is this a bug or am I doing something wrong? > > Thanks in advance > > Dimitris >
