| Re: [jersey-dev] [External] : Question on Jersey licensing |
|
Also,
The standard Jersey runtime jars (non-example jars, non-big-fat-bundle jar) that use 3rd party code also contain NOTICE.markdown files where the licenses for the current jars are listed.
Those are:
jersey-server.jar
jersey-common.jar
jersey-media-jackson.jar
HTH,
Jan
From: jersey-dev <jersey-dev-bounces@xxxxxxxxxxx> on behalf of Michael Lorenz via jersey-dev <jersey-dev@xxxxxxxxxxx>
Sent: Monday, February 24, 2025 9:30 AM To: jersey-dev@xxxxxxxxxxx <jersey-dev@xxxxxxxxxxx> Cc: Michael Lorenz <Michael.Lorenz@xxxxxxxxxxxxxxxxxxx> Subject: [External] : [jersey-dev] Question on Jersey licensing
Dear Eclipse Jersey developer community,
We are currently in the process of clarifying with our open source compliance department whether or not we can use “Jersey Container Servlet” in our application. Questions about the relevant licenses have come up.
While “EPL-2.0” or “GPL-2.0 WITH Classpath-exception-2.0” is specified for the main Jersey project, you have a “## Third-party Content” section in your “NOTICE.md” file in which various other open source projects and their licenses are listed. For example “Angular
JS”, “aopalliance”, “Bootstrap”, ...
It is unclear how these projects relate to Jersey. If there are dependencies to these projects, I would expect them to be declared as dependencies via the Maven POM (direct or transitive) and loaded accordingly, but in my estimation this is not the case (maybe
with the exception of “aopalliance-repackaged”).
Are these optional dependencies, or are parts of these projects included in Jersey? It seems unlikely to me that, for example, client products such as “jQuery” or “Bootstrap” are part of a Java solution, or frameworks such as Angular.
I had already sent an inquiry to license(at)eclipse.org, where I was referred to this mailing list.
Can you help us to understand this?
Kind regards
Michael Lorenz
Mit freundlichen Grüßen Michael Lorenz
|