You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jukka Zitting (Commented) (JIRA)" <ji...@apache.org> on 2011/10/28 19:13:32 UTC
[jira] [Commented] (TIKA-763) Update license metadata
[ https://issues.apache.org/jira/browse/TIKA-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138545#comment-13138545 ]
Jukka Zitting commented on TIKA-763:
------------------------------------
I updated the embedded LICENSE files in revisions 1190449 and 1190451. They are now up to date with our list of dependencies.
Note that during a review of the new dependencies, I encountered the following LGPL files in the NetCDF source tree:
* ucar/nc2/iosp/fysat/Fysatiosp.java
* ucar/nc2/iosp/fysat/FysatHeader.java
* ucar/nc2/dataset/transform/VOceanSG1.java
* ucar/unidata/geoloc/vertical/OceanSG2.java
* ucar/unidata/geoloc/vertical/OceanSG1.java
Ideally we should contact NetCDF and ask them to relicense or replace these files, but that's probably not a short term solution. For tika-app and tika-bundle we could explicitly exclude these files from being included, but I'm not sure what the functional impact of that would be.
The following files are under ALv1.1:
* ucar/unidata/io/bzip2/BZip2Constants.java
* ucar/unidata/io/bzip2/CBZip2InputStream.java
* ucar/unidata/io/bzip2/CRC.java
These can be covered simply by including a copy of the ALv1.1 in the LICENSE files.
> Update license metadata
> -----------------------
>
> Key: TIKA-763
> URL: https://issues.apache.org/jira/browse/TIKA-763
> Project: Tika
> Issue Type: Improvement
> Components: packaging
> Reporter: Jukka Zitting
> Priority: Blocker
> Fix For: 1.0
>
>
> I was going through our dependency tree, and realized that we haven't updated the LICENSE files in tika-app and tika-bundle to reflect some of the more recent additions. We need to bring this license metadata up to date before releasing 1.0.
--
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