[
https://issues.apache.org/jira/browse/UIMA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489013#comment-16489013
]
ASF GitHub Bot commented on UIMA-3385:
--------------------------------------
asfgit commented on issue #1: [UIMA-3385] Update documentation
URL: https://github.com/apache/uima-uimafit/pull/1#issuecomment-391720339
Can one of the admins verify this patch?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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.1.0uimaFIT
>
>
> 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
(v7.6.3#76005)
