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

Jukka Zitting resolved TIKA-565.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.1)
                   1.0

This is now pretty much done. Details in CHANGES.txt:

{quote}
OSGi: The tika-core bundle will now automatically pick up and use any available 
Parser and Detector services when deployed to an OSGi environment. The 
tika-parsers bundle provides such services based on for all the supported file 
formats for which the upstream parser library is available. If you don't want 
to track all the parser libraries as separate OSGi bundles, you can use the 
tika-bundle bundle that packages tika-parsers together with all its upstream 
dependencies. (TIKA-565)
{quote}
                
> Improved OSGi bundling
> ----------------------
>
>                 Key: TIKA-565
>                 URL: https://issues.apache.org/jira/browse/TIKA-565
>             Project: Tika
>          Issue Type: Improvement
>          Components: packaging
>    Affects Versions: 0.10
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 1.0
>
>         Attachments: core-bundle-fix.diff
>
>
> I'd like to add proper integration tests for tika-bundle and expose the Tika 
> facade object as a service so other bundles could access it easily like this:
>     @Reference
>     private Tika tika;
> It would also be nice to allow other OSGi bundles to expose their Parser 
> implementations as pluggable services and have the Tika bundle automatically 
> pick up and use them along with all the embedded parsers it contains.

--
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

        

Reply via email to