Eliminate or replace presumably-spurious LGPL notices.#9
Open
richardfontana wants to merge 1 commit intoprojectodd:masterfrom
Open
Eliminate or replace presumably-spurious LGPL notices.#9richardfontana wants to merge 1 commit intoprojectodd:masterfrom
richardfontana wants to merge 1 commit intoprojectodd:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 a small number of Stilts files that have LGPL notices. Some of these are non-meaningful (like on logging.properties files) while others seem like they must have been included by mistake; as to the former I've deleted the notices, and as to the latter I've replaced the LGPL notices with Apache License 2.0 notices.