[
https://issues.apache.org/jira/browse/UIMA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878863#comment-13878863
]
Luca Foppiano commented on UIMA-3385:
-------------------------------------
I have found this problem as well, here my assumptions:
1. I'm using maven
2. I've placed the file types.txt into the directory
META-INF/org/apache/uima/fit/
3. When I run the pipeline, the file types.txt is not found
I've debugged until the Spring classes and beyond and for me is not clear why
this is not working properly.
My workaround is to use the JVM parameter -D....import_patterns to define the
destination xml to parse.
> Make meta data discovery compatible with fat jars
> -------------------------------------------------
>
> Key: UIMA-3385
> URL: https://issues.apache.org/jira/browse/UIMA-3385
> Project: UIMA
> Issue Type: Improvement
> Components: uimaFIT
> Affects Versions: 2.0.0uimaFIT
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
> Priority: Minor
> Fix For: 2.0.1uimaFIT
>
>
> Most fat jar approaches, e.g. Maven assembly, have problems with resources at
> the same location in the classpath in multiple JARs. E.g. if two JARs being
> bundled into a fat jar have a types.txt file, only one survives.
> One option to fix this would be to change the pattern that uimaFIT uses to
> search for these files, e.g. from
> classpath*:META-INF/org.apache.uima.fit/types.txt to
> classpath*:META-INF/org.apache.uima.fit/**/types.txt
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
