change FeaturePath implementation for empty featurePath strings
---
Key: UIMA-740
URL: https://issues.apache.org/jira/browse/UIMA-740
Project: UIMA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/UIMA-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler closed UIMA-740.
-
Resolution: Fixed
change FeaturePath implementation for empty featurePath strings
File streams are not closed
---
Key: UIMA-741
URL: https://issues.apache.org/jira/browse/UIMA-741
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Affects Versions: 2.3
[
https://issues.apache.org/jira/browse/UIMA-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilo Goetz updated UIMA-741:
-
Affects Version/s: (was: 2.3)
2.2.1
File streams are not closed
I did an experiment where I configered the maven POM for one of our
Eclipse plugins to let maven's eclipse:eclipse update the PDE Manifest.
However, I found a bug in how it treated -SNAPSHOT - it turned
2.3.0.incubating-SNAPSHOT in the maven version into a Manifest entry
[
https://issues.apache.org/jira/browse/UIMA-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilo Goetz reassigned UIMA-741:
Assignee: Thilo Goetz
File streams are not closed
---
UIMA's Soap implementation depends on having the axis classes (from
TomCat?) in its classpath. For normal UIMA deployments, this is
accomplished by adding the needed Jar to the classpath.
For Eclipse and RCP plugin environments, the user's plugin is depending
on the uima-ep-runtime plugin,
