lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-4267) binary packaging should include licenses/
Date Fri, 27 Jul 2012 23:49:35 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424219#comment-13424219
] 

Hoss Man commented on LUCENE-4267:
----------------------------------

bq. we should update build patterns so these directories are in the binary release, its valuable
information on our 3rd party licensing and additional verification for consumers.

"valuable" seems like an understatement ... Unless i'm missing something it's absolutely critical
that we include these licenses.  If we include some third party jar in our binary pacakges,
we damn well better include the license/NOTICE for those jars, or we are probably violating
those licenses.

Personally: i think we should revamp the "licenses/sha checker code" in our build so that
it not only compares the jars with what it finds in /licenses, it should also copy what it
finds in /licenses into the same directory as those jars -- that way our binary packaging
logic in ant should continue to work the same as it did in 4.0.0-ALPHA, and users can always
see at a glance what hte license/NOTICE is for any thirdy-party jar, because it will be sitting
right there next to it in the same directory.

If we don't do this, if thye have to hunt in a special directory in the pacakge to find these
license files, they might not realize that's where they are, and could assume they are ASL2.0
since they are included in an ASF release.
                
> binary packaging should include licenses/
> -----------------------------------------
>
>                 Key: LUCENE-4267
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4267
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
>
> I heavy-committed LUCENE-4262 to enable ivy's sync=true (which means not just get the
right jars, but delete shit that shouldnt be there) to end the whole "clean-jars" issue.
> Its working except for the solr/lib (SOLR-3686) which we must fix for a number of reasons.
> Anyway, because of this I made a lucene/licenses and solr/licenses directories respectively
that contain all the .sha1/license/notice for 3rd party jars, so ivy wouldnt delete them.
> we should update build patterns so these directories are in the binary release, its valuable
information on our 3rd party licensing and additional verification for consumers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message