The Jersey home page states, " The governance policy is the same as the
one used in the GlassFish project. We also use the same two licenses -
CDDL 1.1 and GPL 2 with CPE - so, you can pick which one suites your
needs better." The CPE, or ClassPath Exception, as I understand it, is
an addition to the regular GPLv2 license which clarifies the issue of
"linking". That is to say, just because you /use/ GPLv2 Jersey code,
does not mean your code need be GPLv2 as well. It does still mean,
though, that if you /modify/ the Jersey source you must license it as
GPLv2 and release that code. Other than that, your application code can
be as proprietary as you see fit.
IANAL. :)
On 3/13/12 7:22 AM, Farrukh Najmi wrote:
> IANAL but... CDDL is not viral like GPL2 and does not require
> releasing your source code or releasing your software under CDDL. It
> is re-distribution friendly license.
>
> On 03/13/2012 03:23 AM, adnan.maks_at_gmail.com wrote:
>> My company sells software as an installable on windows and linux.
>> Source code is primary Intellectual property and is not shared or
>> distributed to anyone. We plan to migrate our RPC based implementation
>> to REST-based services. Could you plz let me know if Jersey can be used
>> in our application royalty-free. the licences namely, GPL2 and CDDL
>> require any software using Jersey should release their source code but
>> my company doesn't want to release the source code.
>>
>> Is there a away where we could use Jersey but not release our source
>> code to anyone in any manner?
>>
>
>
--
Jason Lee
Senior Member of Technical Staff
GlassFish Team
Oracle Corporation
Phone +1 405-216-3193
Blog http://blogs.steeplesoft.com