[
https://issues.apache.org/jira/browse/UIMA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974770#comment-13974770
]
Richard Eckart de Castilho commented on UIMA-3385:
--------------------------------------------------
Hugo, could you provide some context/motivation for this kind of packaging? I
gather that people building fat-jars do so in order to easily transfer and run
an (uimaFIT) application to some other machine. Under which circumstances would
somebody prefer the slim approach?
> 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.2#6252)
