[Jersey] Re: Jersey Repackaging

From: Mark Thornton <>
Date: Mon, 25 Aug 2014 21:06:01 +0100

And yet the developers chose to repackage over updating to current
versions. In my own development , I have slipped behind on versions for
several dependencies. Other work has a higher priority (at least until
something breaks).


On Monday, 25 August 2014, cowwoc <> wrote:

> Part of the solution is for Jersey to be more proactive in updating its
> dependencies. Keeping up-to-date with the latest releases isn't a lot of
> work.
> Gili
> On 25/08/2014 3:42 PM, Mark Thornton wrote:
> Perhaps because not all build systems in use have something equivalent to
> shade. Also where the version used by jersey is particularly old (such as
> asm), far too many users would have to do the same repackaging.
> Mark Thornton
> On Monday, 25 August 2014, Robert DiFalco <
> <javascript:_e(%7B%7D,'cvml','');>> wrote:
>> Does the Jersey repackaged stuff mean that if I am using Guava in my
>> project that there will be duplicate classes for all the stuff Jersey
>> repackaged? Why is this a better idea than letting people use shade or
>> something similar?