[
https://issues.apache.org/jira/browse/TIKA-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535255
]
Thilo Goetz commented on TIKA-41:
---------------------------------
There's a similar issue in Eclipse (I think it has the same root cause). After
doing mvn eclipse:eclipse, I end up with an invalid .classpath file in Tika
that gives me this error: Cannot nest output folder
'tika/target/classes/org/apache/tika' inside output folder
'tika/target/classes'. I can manually fix the classpath, but then, just like
for Keith, the test cases don't go through. I have not investigated further.
I would like to throw in my support for a build environment that supports both
maven and the popular IDEs. We do this in UIMA, and it does cause us some
headaches now and then, but for us seamless Eclipse support was non-negotiable.
I understand your reluctance to make compromises for the support of IDEs, but
many developers do use them. The easier it is to set up the development env.
in your favorite IDE, the more likely you are to get more contributors. If
it's just a question of maintaining a parallel directory structure in the
resources and the target directories, I would consider this a small sacrifice.
Then again, opinions may vary ;-)
And just to be clear, when working in Eclipse (just for example), I don't build
with maven. I do a svn extract from inside eclipse, then I go to the command
line and do mvn clean install; mvn eclipse:eclipse. After that, I expect to be
all set to work in Eclipse (unless I create new dependencies of course).
Just something to consider...
> 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
> Assignee: Jukka Zitting
> 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.
