incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jukka Zitting <jukka.zitt...@gmail.com>
Subject Re: Q: including notice for binary release of artifacts that are brought in via Maven?
Date Tue, 31 Jan 2012 11:07:18 GMT
Hi,

On Tue, Jan 31, 2012 at 2:49 AM, Jakob Homan <jghoman@gmail.com> wrote:
>  Great, thanks.  Using this method, I get a file layout similar to:
>  giraph-0.1-SNAPSHOT-bin.tar.gz
>      NOTICE (without appended text for dep1 and dep2)
>      LICENSE (without appended text for dep1 and dep2)
>      bin/
>      lib/
>         dep1.jar
>         dep2.jar
>         giraph.jar
>            META-INF/
>               NOTICE (with appended text for dep1 and dep2)
>               LICENSE (with appended text for dep1 and dep2)
>
> This matches with what I see when I checkout the jackrabbit-standalone
> code and do a package command from maven there.  I just want to verify
> that this will past muster with incubator.  This configuration
> satisfies the requirement for those notices/licenses to be included?

The general idea is that the NOTICE/LICENSE pair of an artifact should
cover all the bits included inside that artifact.

If giraph.jar doesn't embed dep1 and dep2, then there's no need to
mention them in the NOTICE/LICENSE pair of that jar.

Instead, since you are including dep1 and dep2 inside
giraph-bin.tar.gz, they should be covered by the NOTICE/LICENSE pair
of the tarball.

If you look inside the jackrabbit-standalone jar, you'll notice that
it actually contains all the external components mentioned in the
NOTICE/LICENSE files.

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message