[🚀 Feature]: Include LICENSE and copyright NOTICE inside all packages and binary releases
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 752
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 8
Description
Description
In my mind it is good practice to deploy the LICENSE and NOTICE files inside the binaries to ensure the "4. Redistribution." section of the LICENSE file is fulfilled. A lot of project are doing so, e.g. JUnit, opentest4j, Johnzon, ... just look at the "META-INF" folder of the jars.
This is a copy of the selenium issue https://github.com/SeleniumHQ/selenium/issues/16113 as this makes sense (in my mind) for appium too.
Have you considered any alternatives or workarounds?
Deploy the files myself.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the project’s packaging and binary release configuration to find where published packages and binaries are assembled. Verify which artifacts are covered and ensure each includes LICENSE and NOTICE; done when the files are present in all requested distributions, with packaging checks passing if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100