It's not possible to use less of Jersey. I'm all for changes that make sense, like switching JSON libraries due to licensing issues. However, a JAX-RS framework is like an NIO framework -- the service code may be structured similarly but there are substantial functional and semantic differences between them.
We chose Jersey because it was the reference JAX-RS framework and something that would "just work". I would not stand in the way of a port to another framework but have no plans (or available time) to contemplate such a large undertaking at this time. - Andy > From: Stack > Subject: Re: jersey (stargate dependency) is insane! > To: hbase-dev@hadoop.apache.org, tho...@koch.ro > Date: Monday, May 3, 2010, 9:00 PM > Thanks for looking into this Thomas. If there are not > currently JAX-RS implementations in Debian, its a bit of > a problem. I just presumed the jersey stuff reasonable. > What if we updated to a newer version? Or used less of > it? > > St.Ack > > On Mon, May 3, 2010 at 12:22 PM, Thomas Koch wrote: > > Hi, > > > > I've problems packaging the stargate (REST) contrib > > for HBase. The used JAX-RS implementation jersey has > > so many yet "undebianized" dependencies, that I > > won't be able to include this contrib anytime soon in > > the upcoming Debian package.
