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 (JIRA)" <ji...@apache.org> on 2008/03/28 00:12:24 UTC

[jira] Commented: (TIKA-137) Move CLI and GUI into separate sub-modules

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

Jukka Zitting commented on TIKA-137:
------------------------------------

I'd resolve this as Won't Fix.

The CLI and GUI classes add no extra dependencies and cost only a few extra kilobytes in the Tika jar file. I don't see how keeping them around in the same component is harmful.

> Move CLI and GUI into separate sub-modules
> ------------------------------------------
>
>                 Key: TIKA-137
>                 URL: https://issues.apache.org/jira/browse/TIKA-137
>             Project: Tika
>          Issue Type: Improvement
>          Components: config, general
>    Affects Versions: 0.2-incubating
>         Environment: All.
>            Reporter: Karl Heinz Marbaise
>            Priority: Minor
>
> It would be a good choice based on my point of view that you move the CLI and GUI parts into separate modules. This will separate the CLI/GUI parts from the real library parts.
> This would result in the following structure:
> Root
>   +--- CLI
>   !
>   +--- GUI
>   !
>   +--- LIB
> The LIB represents the real Tika-Framework which can be used by any other application without having integrated of any classes of GUI/CLI which a not needed.

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