I have always assume that it is safe to you because its license scheme is
exactly like JAXB and JAXB is bundled together with the standard JDK and
JRE.
dc
On Thu, Jan 9, 2014 at 11:38 AM, Michael Iles <michael.iles_at_gmail.com>wrote:
> CDDL is sort of a middle ground: it has a similar source-code
> requirement to GPL (if you modify Jersey source then you need to make
> your changes available) but it's not viral, so you can license your
> own code as you see fit and you don't need to release your own code if
> you don't want to.
>
> Mike.
>
> (I'm not a lawyer. Consult with your lawyers.)
>
> On 9 January 2014 11:11, Nasir Rasul <nasir.rasul_at_gmail.com> wrote:
> > @Wu: My understanding is that if you make changes in core jersey, you are
> > required to make those changes openly so others can benefit from your
> > contribution, just like you were able to benefit form others'
> contribution
> > by using jersey in the first place.
> >
> > If you use jersey to build something and profit, you are allowed to even
> > charge on your app. You might need to attribute that you used jersey (not
> > sure about that).
> >
> > - Nasir
> >
> >
> > On Thu, Jan 9, 2014 at 11:07 AM, Jack Lista <jackalista_at_gmail.com>
> wrote:
> >>
> >> Not dead sure but I suspect you're misunderstanding something, Jersey is
> >> in use in all kinds of commercial projects...
> >>
> >> -=j=-
> >>
> >>
> >> On Wed, Jan 8, 2014 at 10:43 PM, mingyao Wu <mingwu_at_adobe.com> wrote:
> >>>
> >>> I want to use Jersey lib to implement a commercial RESTful web service.
> >>> And I don't want the commercial project become an open source project.
> It
> >>> looks like conflict with the GPL license which Jersey applied to. What
> can I
> >>> do to get the license of using Jersey in a commercial project?
> >>>
> >>>
> >>> Thanks
> >>> Mingyao
> >>>
> >>
> >
>