[
https://issues.apache.org/jira/browse/TIKA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved TIKA-184.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.3
Fixed in revision 726539.
> Avoid the <resource/> entry on ${basedir}
> -----------------------------------------
>
> Key: TIKA-184
> URL: https://issues.apache.org/jira/browse/TIKA-184
> Project: Tika
> Issue Type: Improvement
> Components: general
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 0.3
>
>
> At least the m2eclipse Eclipse plugin is having trouble with the <resource/>
> entry we use to include the LICENSE, NOTICE, and README files in META-INF of
> the resulting jar artifact. The problem is ${basedir} (i.e. the root of the
> whole Tika checkout) used as the resource directory, which causes Eclipse to
> treat the whole Tika checkout as a source directory and prevents nesting of
> the real src/main/java and other source directories.
> We could achieve the same effect (bundling of the META-INF files) for example
> by separately configuring the copy-resources goal of the
> maven-resources-plugin.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
