ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Matèrne (JIRA) <>
Subject [jira] Created: (IVY-893) <ivy:licenselist/> should generate a list of used licenses
Date Wed, 03 Sep 2008 07:45:46 GMT
<ivy:licenselist/> should generate a list of used licenses

                 Key: IVY-893
             Project: Ivy
          Issue Type: New Feature
          Components: Ant
            Reporter: Jan Matèrne

Based on the information in Ivy-files or POMs the Ivy Anttask <licenselist todir="" configuration=""/>
should create a license file for each dependent component specified in the used configuration.

This was discussed on the mailinglist:


-----Ursprüngliche Nachricht-----
Von: Xavier Hanin 
Gesendet: Mittwoch, 3. September 2008 09:18
Betreff: Re: Creating a list of licenses

On Wed, Sep 3, 2008 at 7:45 AM, <Jan.Materne@> wrote:

> Ivy resolves dependencies and transitive dependencies.
> If my project P depends on A and B and B on C I will get   P --> A, B --> C  and
download A,B and C.
> In Java projects these are typically jar-files.
> Each of these have a license (Default=unspecified).
> Could I get a list of licenses?
>    <ivy:createlist todir="build/licenses"/>
>    build/licenses: P.license, A-1.0.license, B-4.7.license, C-3.0.0.alpha.license
> (I hope it's clear what I mean ...)
> I think it's not possible at the moment as these license information are
> not available in a standardized way.
> But if I set up a company repository I could store these information.
>    //repository/A/1.0 : a.jar  ivy.xml   license.txt

Ivy already defines a way to define one or multiple licenses in your Ivy file. The license
isn't considered as an artifact, but you can have a URL to the license:

The dependency report collects information on the licenses for each dependency, so doing what
you want based on this report is pretty easy. It would be interesting to make this part of
Ivy since it's probably useful for many. Could you open an issue for that? And maybe we should
find a better name than createlist for the task, sg more specific to license. Why not <ivy:licenselist
todir="build/licenses" /> ?

One thing I realize is that it seems we don't parse this information in poms, so you won't
get license information when you use poms to describe your modules. I'll fix this.



-----Ursprüngliche Nachricht-----
Von: Johannes Stamminger [mailto:Johannes.Stamminger@] 
Gesendet: Mittwoch, 3. September 2008 09:25
Betreff: Re: Creating a list of licenses

We faced same problem and handle the licenses as another artifact in our company repository:
we defined a configuration "deploy" in which each lib provides it's license (for simplicity
stored in rep as <jar name>.license) with type set to license. In ant build environment
we access those with cachefilesets (for copying to release dir).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message