[
https://issues.apache.org/jira/browse/TIKA-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532876
]
Keith R. Bennett commented on TIKA-41:
--------------------------------------
Chris -
> ...mandating that the build time representation of the tika library
> (currently a jar file) look 100% the same as the source tree
> takes us down a slippery slope...
This mandate only applies to the src directory tree; if there are files we want
to associate with the project for CM purposes, but we do not need or want to be
under Maven's control, then maybe we can create another directory for that? So
under tika, we'd have the Maven style directories (src, target (when built),
etc.), and then other directories as we need them?:
tika
--- src
--- foo
I don't think there's anything in Maven that would touch anything in a
directory unknown to it, is there? When it does a clean, it only removes the
target directory tree to my knowledge.
Regarding Jukka's point about IDE's, I think he was referring to the IDE
itself, not the IDE user. That is, the IDE can infer from the files'
placements in the directory tree what they are and what needs to be done with
them, as opposed to it having to figure out a directive in a POM file.
Regards,
Keith
> 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
>
>
> 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.
