Add explicit license information to packages' POM file #413
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Having the license information in the POM file allows it to be self-contained. A glance to it is enough to determine licensing. This is especially important for private artifact mirrors, that often do not allow closed-source, source-available or hard-copyleft libraries to be used. Without the license information on the POM file, some of these repositories will deny mirroring this library.
|
Instead of copying to each file, would it not work if you add it to the parent pom? (EDIT: no wait we already have the license in the top level java11-oss pom ) |
rbygrave
approved these changes
Aug 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Having the license information in the POM file allows it to be self-contained. A glance to it is enough to determine licensing.
This is especially important for private artifact mirrors, that often do not allow closed-source, source-available or hard-copyleft libraries to be used. Without the license information on the POM file, some of these repositories will deny mirroring this library.
I'm trying to mirror the Avaje libraries in a private artifact repository, but am running into the issue of the repository not being able to extract the license from the repository (likely not a part of the JARs), which then means that it doesn't mirror the libraries correctly.