Closed lucasvc closed 3 years ago
I think we can do that in the current codebase (no release planned as of now) because the detail page of the JSR also says it's "a BSD 3-Clause License". Thanks for the suggestion.
Other libraries related to the JSR 385 suffer this same issue,
should I open corresponding issue in each of them?
Current POM indicates as license information,
But readme badge clearly states as BSD3 license, leaving the POM not coherent and ambiguous (as the BSD multiple flavours).
So when using tools to analise licenses (i.e., jk1/Gradle-License-Report) requires manual review of the corresponding license.
Maybe adding in the name a term like,
would make coherent visual documentation and POM file, moreover would help automated tools.