Skip to content
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 add LICENSE as META-INF/LICENSE, add Bundle-License header #264

Open
vlsi opened this issue Jun 29, 2019 · 2 comments · May be fixed by #399
Open

Please add LICENSE as META-INF/LICENSE, add Bundle-License header #264

vlsi opened this issue Jun 29, 2019 · 2 comments · May be fixed by #399

Comments

@vlsi
Copy link

vlsi commented Jun 29, 2019

  1. Thanks for Hamcrest

  2. Current hamcrest.jar are hard to bundle into other software due to missing licensing information.

Suggested changes are:

2.1) Package license as META-INF/LICENSE. Current one is LICENSE.txt, and de-facto standard is META-INF/LICENSE. The license files packaged at the root cause problems with Android.
Basically whoever makes an uberjar they have to implement "license merger", and typically they configure for META-INF/LICENSE.
2.2) Please add Bundle-License: BSD-3-Clause manifest entry (where BSD-3-Clause is SPDX identifier, see https://osgi.org/specification/osgi.core/7.0.0/framework.module.html#framework.module-bundle-license )
Unfortunately, there are lots of BSD-style licenses, and it is hard to tell what "New BSD License" means.
2.3) Even though 2.1 and 2.2 would be great, you might want to use BSD-3-Clause for <licence><name> tag in pom.xml. The use of SPDX in pom is not common yet, however BSD-3-Clause there would help even humans.

@tumbarumba
Copy link
Member

This seems like a reasonable improvement. Are you able to create a pull request with these changes?

vlsi added a commit to vlsi/JavaHamcrest that referenced this issue Apr 29, 2023
vlsi added a commit to vlsi/JavaHamcrest that referenced this issue Apr 29, 2023
@vlsi
Copy link
Author

vlsi commented Apr 29, 2023

@tumbarumba , here's a PR: #399

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants