On Oct 13, 2009, at 11:38 AM, Felipe Gaścho wrote:
> The below dependencies are suspicious for me. I still need that for
> the latest jersey release (1.1.3-ea) ?
>
IIRC those dependencies were suggested to work around an issue with
deployment failure and were not meant to suggest they were in any way
required.
> <dependency>
> <groupId>com.sun.xml.stream</groupId>
> <artifactId>sjsxp</artifactId>
> <version>1.0.1</version>
> </dependency>
> <dependency>
> <groupId>net.sf.saxon</groupId>
> <artifactId>saxon-dom</artifactId>
> <version>8.7</version>
> </dependency>
> <dependency>
> <groupId>net.sf.saxon</groupId>
> <artifactId>saxon-xpath</artifactId>
> <version>8.7</version>
> </dependency>
>
>
> Suggestion: it would be really useful if the front page of Jersey
> present always the latest maven dependencies both for server and
> client side of Jersey..
That would clutter the main page. Click on the download button to see
dependencies for 1.1.2-ea
For 1.1.3-ea it has moved:
https://jersey.dev.java.net/nonav/documentation/1.1.3-ea/user-guide.html
#d4e742
Paul.
> It is a seasonal pain to look for those
> versions.. :) If I can just copy paste from a reliable source, it
> would promote more adopter.. The suggestion if valid for all Glassfish
> portfolio :)
>
>
> --
> Looking for a client application for this service:
> http://fgaucho.dyndns.org:8080/arena-http/wadl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>