[jira] Created: (TIKA-145) Separate NOTICEs and LICENSEs for binary and source packages

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (TIKA-145) Separate NOTICEs and LICENSEs for binary and source packages

Clark Perkins (Jira)
Separate NOTICEs and LICENSEs for binary and source packages
------------------------------------------------------------

                 Key: TIKA-145
                 URL: https://issues.apache.org/jira/browse/TIKA-145
             Project: Tika
          Issue Type: Improvement
          Components: packaging
            Reporter: Jukka Zitting
            Assignee: Jukka Zitting
             Fix For: 0.2-incubating


The Tika source tree or a source release does not contain our dependencies, so the associated LICENSE and NOTICE files do not need to cover them.

However, the Maven build automatically includes the depencencies in the -standalone jar, which thus should contain LICENSE and NOTICE files that do cover the dependencies.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (TIKA-145) Separate NOTICEs and LICENSEs for binary and source packages

Clark Perkins (Jira)

     [ https://issues.apache.org/jira/browse/TIKA-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved TIKA-145.
--------------------------------

    Resolution: Fixed

Resolved in revision 669315.

> Separate NOTICEs and LICENSEs for binary and source packages
> ------------------------------------------------------------
>
>                 Key: TIKA-145
>                 URL: https://issues.apache.org/jira/browse/TIKA-145
>             Project: Tika
>          Issue Type: Improvement
>          Components: packaging
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.2-incubating
>
>
> The Tika source tree or a source release does not contain our dependencies, so the associated LICENSE and NOTICE files do not need to cover them.
> However, the Maven build automatically includes the depencencies in the -standalone jar, which thus should contain LICENSE and NOTICE files that do cover the dependencies.

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