Fix "Apache License, Version 2.0" spelling #3471
Closed
Conversation
This file contains 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
|
Thanks! I'll import this |
|
This license naming format is used in multiple pom files. |
|
Thanks! I have amended my commit. |
Merged
ronshapiro
pushed a commit
that referenced
this pull request
May 28, 2019
There are many Java libraries licensed under "Apache License, Version 2.0" that do not use its official spelling. This causes issues like https://issues.apache.org/jira/browse/MPIR-382: with every library defining its own spelling, it's difficult in large projects to have a clear view of all licenses in use. This PR changes the license spelling to the official one, as advised by Maven developers. Closes #3471 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=249139087
|
Whoops I already submitted this. I'll submit another. |
|
As an aside - what if you grouped licenses based on URL and not based on title? Wouldn't that dedupe well? |
ronshapiro
pushed a commit
that referenced
this pull request
May 28, 2019
There are many Java libraries licensed under "Apache License, Version 2.0" that do not use its official spelling. This causes issues like https://issues.apache.org/jira/browse/MPIR-382: with every library defining its own spelling, it's difficult in large projects to have a clear view of all licenses in use. This PR changes the license spelling to the official one, as advised by Maven developers. Closes #3471 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=249139087
cpovirk
pushed a commit
that referenced
this pull request
Jun 3, 2019
Closes #3471 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=250289501
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.
There are many Java libraries licensed under "Apache License, Version 2.0" that do not use its official spelling.
This causes issues like https://issues.apache.org/jira/browse/MPIR-382: with every library defining its own spelling, it's difficult in large projects to have a clear view of all licenses in use.
This PR changes the license spelling to the official one, as advised by Maven developers.