You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@any23.apache.org by "Paolo Castagna (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/02/16 14:23:59 UTC
[jira] [Issue Comment Edited] (ANY23-37) LGPL'ed components cannot
be included in distribution packages
[ https://issues.apache.org/jira/browse/ANY23-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209338#comment-13209338 ]
Paolo Castagna edited comment on ANY23-37 at 2/16/12 1:23 PM:
--------------------------------------------------------------
Hi Lewis, considering the context (i.e. Apache (and you as committer in both projects)) it makes a lot of sense for a project such as Any23 to use Nutch as crawler.
If that is possible and a comparable amount of work, it certainly makes even more sense.
I had not looked at the details, in particular at what it would take to get rid of the dsiutils dependency and/or ANY23-47.
was (Author: castagna):
Hi Lewis, considering the context (i.e. Apache (and you as committer in both projects)) it makes a lot of sense for a project such as Any23 to use Nutch as crawler.
It that is possible and a comparable amount of work, it certainly makes sense.
I had not looked at the details, in particular at what it would take to get rid of the dsiutils dependency and/or ANY23-47.
> LGPL'ed components cannot be included in distribution packages
> --------------------------------------------------------------
>
> Key: ANY23-37
> URL: https://issues.apache.org/jira/browse/ANY23-37
> Project: Apache Any23
> Issue Type: Bug
> Reporter: Simone Tripodi
> Priority: Critical
>
> While reviewing dependencies license, I noticed that the it.unimi.dsi:dsiutils:2.0.1 transitive dependency is released under LGPL release, so it cannot be included in the non-maven binary archives.
> A first turnaround solution could be avoiding it is included and reporting it in the README.
--
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