Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Is there a Gradle License Plugin or What is the best way to handle Licenses of Dependencies? [closed]

I'm about to release a little hobby open source project. Since it bundles a bunch of dependencies I have to take care of the various license requirements. Most of the time this means adding some license file to the distribution (at least that is my understanding, but you never know about lawyers).

Is there a Gradle plugin that takes care of that, at least for the common Open Source Licenses?

If there is no Gradle plugin, is there an accepted approach to handle this, like listing all the jars + the license after the own license, or putting a *.license file next to each *.jar file or something?

like image 388
Jens Schauder Avatar asked Dec 28 '12 15:12

Jens Schauder


People also ask

During which activity do we capture the licensing dependencies details?

At deployment time the license info of all dependencies is read - if unapproved or unknown licenses are found an email alert with the information is sent to preconfigured addresses.

Is gradle free for commercial use?

Do the Services cost anything? The Gradle Products available on our website are currently provided free of charge.


1 Answers

There is a Gradle License Plugin on Github (I'm the maintainer). Currently the plugin only adds and removes License headers to your source files. There is no support yet for adding the licenses of jar dependencies to a LICENSE file, but that shouldn't be too hard to add, just haven't had the time yet.

like image 68
Hiery Nomus Avatar answered Oct 04 '22 23:10

Hiery Nomus