[jira] Created: (TIKA-219) Split Tika to separate modules

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

[jira] Created: (TIKA-219) Split Tika to separate modules

JIRA jira@apache.org
Split Tika to separate modules
------------------------------

                 Key: TIKA-219
                 URL: https://issues.apache.org/jira/browse/TIKA-219
             Project: Tika
          Issue Type: Improvement
          Components: general
            Reporter: Jukka Zitting
            Assignee: Jukka Zitting
             Fix For: 0.4


As discussed recently on the mailing list [1], it would be good to split Tika to components based on use cases and external dependencies.

The proposed split is:

* tika-core - core parts of Tika; everything but cli, gui, and the parser.* packages
* tika-parsers - format-specific parser classes; with dependencies to external libraries
* tika-app - depends on all of the above; adds cli and gui; standalone jar packaging

[1] http://markmail.org/message/tavirkqhn6r2szrz

--
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] Commented: (TIKA-219) Split Tika to separate modules

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/TIKA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703632#action_12703632 ]

Chris A. Mattmann commented on TIKA-219:
----------------------------------------

+1, this sounds great, Jukka.

Cheers,
Chris


> Split Tika to separate modules
> ------------------------------
>
>                 Key: TIKA-219
>                 URL: https://issues.apache.org/jira/browse/TIKA-219
>             Project: Tika
>          Issue Type: Improvement
>          Components: general
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.4
>
>
> As discussed recently on the mailing list [1], it would be good to split Tika to components based on use cases and external dependencies.
> The proposed split is:
> * tika-core - core parts of Tika; everything but cli, gui, and the parser.* packages
> * tika-parsers - format-specific parser classes; with dependencies to external libraries
> * tika-app - depends on all of the above; adds cli and gui; standalone jar packaging
> [1] http://markmail.org/message/tavirkqhn6r2szrz

--
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-219) Split Tika to separate modules

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Jukka Zitting resolved TIKA-219.
--------------------------------

    Resolution: Fixed

The trunk is now split to modules as proposed above. There may be some issues that still need to be ironed out, but we can use separate issues to track those. Resolving this as Fixed.

> Split Tika to separate modules
> ------------------------------
>
>                 Key: TIKA-219
>                 URL: https://issues.apache.org/jira/browse/TIKA-219
>             Project: Tika
>          Issue Type: Improvement
>          Components: general
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.4
>
>
> As discussed recently on the mailing list [1], it would be good to split Tika to components based on use cases and external dependencies.
> The proposed split is:
> * tika-core - core parts of Tika; everything but cli, gui, and the parser.* packages
> * tika-parsers - format-specific parser classes; with dependencies to external libraries
> * tika-app - depends on all of the above; adds cli and gui; standalone jar packaging
> [1] http://markmail.org/message/tavirkqhn6r2szrz

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