-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please bundle LICENSE file to the published jar artifacts #472
Comments
Hi @vlsi, |
Thanks, 2.2.1 and 3.1.1 include the licenses indeed. |
vlsi
added a commit
to vlsi/jmeter
that referenced
this issue
Dec 14, 2021
vlsi
added a commit
to vlsi/jmeter
that referenced
this issue
Dec 14, 2021
vlsi
added a commit
to vlsi/jmeter
that referenced
this issue
Dec 14, 2021
vlsi
added a commit
to vlsi/jmeter
that referenced
this issue
Dec 25, 2021
vlsi
added a commit
to apache/jmeter
that referenced
this issue
Dec 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
org.jetbrains.lets-plot:plot-config-portable-jvm:2.2.0 says it is MIT-licensed, however,
It references an invalid license: https://opensource.org/licenses/MIT. The thing is there's no generic text for MIT license, and the actual uses of MIT always customize copyright owner and copyright year, so all "MIT licenses" are different.
License text might vary over time (e.g. copyright owners might vary), so the ones who bundle MIT-licensed software need to carefully follow the exact license text for the particular version. For instance, if Apache JMeter bundles
lets-plot
, then MIT license requires thatcopyright notice shall be included in all copies or substantial portions of the Software
. In other words, it requires to include the copy of the license with the appropriate copyright notice.I would suggest including the license text as
META-INF/LICENSE
so the ones who consume (and redistribute) the jar know the license for the given artifact.Here is the list of the artifacts without a corresponding license file:
The text was updated successfully, but these errors were encountered: