tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TIKA-41) Resource files occur twice in jar file.
Date Sun, 07 Oct 2007 20:23:50 GMT

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

Jukka Zitting updated TIKA-41:

    Attachment: TIKA-41.patch

Attached a patch (TIKA-41.patch) that uses declarative Maven configuration instead of <copy/>
directives to place the resources in the correct location. I guess this should satisfy all
the requirements expressed here.

> Resource files occur twice in jar file.
> ---------------------------------------
>                 Key: TIKA-41
>                 URL: https://issues.apache.org/jira/browse/TIKA-41
>             Project: Tika
>          Issue Type: Improvement
>    Affects Versions: 0.1-incubator
>            Reporter: Keith R. Bennett
>            Priority: Minor
>             Fix For: 0.1-incubator
>         Attachments: TIKA-41.patch
> The Tika and Mime config files occur in two places in the jar file.  This is because
they are not stored in our src/test/resources directory tree in the same place that they need
to be in the target/classes directory tree, and there is a copy directive in the POM file
that copies the files to different directory.
> For example, tika-config.xml is in src/main/resources, but needs to go to target/class/org/apache/tika.
 Maven automatically copies the files in src/main/resources to the same location in target/classes,
so tika-config.xml is copied to target/classes.  Then, the copy directive in the POM file
copies the file to target/classes/org/apache/tika.  So the file is copied twice.
> I recommend the following to fix this:
> * Move tika-config.xml to src/main/resources/org/apache/tika.
> * Move tika-mimetypes.xml to src/main/resources/org/apache/tika/mime.
> * Remove the copy directives for the above two from the POM file.

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

View raw message