bintray / gradle-bintray-plugin

Apache License 2.0
1.28k stars 196 forks source link

Missing <licenses> elements in pom.xml #114

Open gfx opened 8 years ago

gfx commented 8 years ago

I use this plugin via https://github.com/novoda/bintray-release and have find that there are no <licenses/> elements in pom.xml.

For example, here is my library:

https://bintray.com/gfx/maven/orma/2.4.2/view#files/com/github/gfx/android/orma/orma/2.4.2

and the pom.xml is like this:

<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.github.gfx.android.orma</groupId>
  <artifactId>orma</artifactId>
  <version>2.4.2</version>
  <packaging>aar</packaging>
  <dependencies>...</dependencies>
</project>

Bintray itself has licenses metadata like this: https://bintray.com/gfx/maven/orma/2.4.2/ ("Apache-2.0")

I think licenses is inevitable to use libraries easily, so I'd like to include <licenses/> elements in pom.xml; I'm not sure this plugin should be responsible for the issue though.

eyalbe4 commented 8 years ago

Which of the Gradle plugins are you using to upload your artifacts to Bintray? https://github.com/bintray/gradle-bintray-plugin or https://github.com/novoda/bintray-release

Also, did you add the license information to your Gradle build script? If you did, then the gradle-bintray-plugin (the first one of the 2 mentioned above) should create your pom file with the license information and upload it to Bintray.

gfx commented 8 years ago

I use bintray-release v0.3.4, which uses gradle-bintray-plugin v1.3.1

And I do add licenses to gradle build script; thus bintray shows licenses for my library.