[
https://issues.apache.org/jira/browse/UIMA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878900#comment-13878900
]
Richard Eckart de Castilho edited comment on UIMA-3385 at 1/22/14 5:50 PM:
---------------------------------------------------------------------------
Other software tends to use just a simple directory under META-INF or not even
any directory:
* Maven: META-INF/maven/... (actually
META-INF/maven/<groupId>/<artifactId>/...)
* CXF: META-INF/cxf/...
* Spring: META-INF/spring.schemas
I used the long name, because I fear the short names bear to much potential for
conflicts. Before changing the name in any way, there should be convincing
reasons and a really good best-practice. Since the time that uimaFIT has this
feature, you're actually the first that complains about this particular aspect
(flat naming vs. hierarchic naming).
Given the other requirements in this issue, I'd probably tend to switch to
something like META-INF/uimafit/<groupId>/<artifactId>/types.txt … but don't
nail me down on this just yet.
Let's wait for some more feedback from other people.
was (Author: rec):
Other software tends to use just a simple directory under META-INF or not even
any directory:
* Maven: META-INF/maven/... (actually
META-INF/maven/{groupId}/{artifactId}/...)
* CXF: META-INF/cxf/...
* Spring: META-INF/spring.schemas
I used the long name, because I fear the short names bear to much potential for
conflicts. Before changing the name in any way, there should be convincing
reasons and a really good best-practice. Since the time that uimaFIT has this
feature, you're actually the first that complains about this particular aspect
(flat naming vs. hierarchic naming).
Given the other requirements in this issue, I'd probably tend to switch to
something like META-INF/uimafit/{groupId}/{artifactId}/types.txt … but don't
nail me down on this just yet.
Let's wait for some more feedback from other people.
> 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)
