www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LEGAL-28) LICENSE/NOTICE and binary, source, javadocs, tests jars
Date Fri, 20 Jun 2008 13:53:45 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606761#action_12606761
] 

Daniel Kulp commented on LEGAL-28:
----------------------------------


Why would the test jars need that unless you are actually copying JUnit code into your test
tree?   You aren't shipping the JUnit jar or any junit code.   Thus, the NOTICE would not
be needed.

Now, should the remote-resources generate a separate "DEPENDECIES" file for the test that
includes that?  Maybe.  But that would be a feature request for remote-resources.   There
is no legal requirement to have the DEPENDENCIES file there at all.

> LICENSE/NOTICE and binary, source, javadocs, tests jars
> -------------------------------------------------------
>
>                 Key: LEGAL-28
>                 URL: https://issues.apache.org/jira/browse/LEGAL-28
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Stefano Bagnara
>
> Most m2 based projects creates multiple jars for each module they release and the resulting
jars are published to maven repositories.
> Some of them are:
> jar: the "standard output", contaiinng binary for the project
> source-jar: sources for the classes included in the above jar (for reference, not for
build purpose).
> javadoc-jar: javadocs about the classes included in the jar
> test-jar: tests binary for the jar library
> Most m2 projects use org.apache:apache-jar-resource-bundle:1.4 resource bundle and creates
a very simple LICENSE/NOTICE that is appropriate for the "jar" package, but this file also
ends up in the other packages I described.
> My concern is: what should we care for?
> javadoc-jar: what are the rules for a LICENSE/NOTICE about javadocs? are they equal to
the binary classes they document?
> source-jar: is there any special rule or the LICENSE/NOTICE that works for the binary
is also ok for their java sources?
> test-jar: this one seems to deserve a custom LICENSE/NOTICE because it include really
something different from the jar: e.g: most project would probably need at least this in the
NOTICE:
> ----------
> This product includes/uses software, JUnit (http://www.junit.org/),
> developed by Kent Beck, Erich Gamma, and David Saff
> License: Common Public License Version 1.0  (http://www.opensource.org/licenses/cpl.php)
> ---------
> Is this paranoia or something we should be care of?
> Maybe you already discussed this issue and a policy is already in place, but I didn't
find anything in www.apache.org and also with few searches in legal-discuss archives.

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


---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message