Skip to content

add support for LICENSE properties in addition to LICENCE #272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 20, 2021

Conversation

gabrielittner
Copy link
Collaborator

closes #252

I've changed the readme you LICENSE because that matches the spelling Gradle uses in their API.

Verified

This commit was signed with the committer’s verified signature. The key has expired.
gabrielittner Gabriel Ittner
@gabrielittner gabrielittner merged commit 9dfa4e0 into master Jun 20, 2021
@vanniktech vanniktech deleted the license branch June 20, 2021 15:49
ajalt pushed a commit to ajalt/mordant that referenced this pull request Jan 16, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Hello, I am using this library in one of the projects and during the
license compliance check I noticed that its POM looks a bit strange - it
has 2 **license** blocks inside the
[licenses](https://repo1.maven.org/maven2/com/github/ajalt/mordant/mordant-jvm-jna-jvm/3.0.1/mordant-jvm-jna-jvm-3.0.1.pom)
block.

<details><summary>POM part</summary>
<p>

```xml
<licenses>
  <license>
    <name>Apache-2.0</name>
    <url>https://www.apache.org/licenses/LICENSE-2.0</url>
  </license>
  <license>
    <distribution>repo</distribution>
  </license>
</licenses>
```

</p>
</details> 

Right now there are two versions of license properties are used
(LICEN**S**E and LICEN**C**E) in gradle.properties. POM_LICENSE_DIST is
added as a separate license because of the following change in
gradle-maven-publish-plugin:
vanniktech/gradle-maven-publish-plugin#272.

I renamed all the options to LICEN**S**E to match the naming in Gradle
API and the license itself.

Please, let me know If I have missed anything in the PR (update the
changelog for example)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LICENCE -> LICENSE?
2 participants