Seems like this (telling people to use FileLocator.java), together with some of the reminders you've sent in the last month to dev@, would make good additions to a Best (cTAKES) Practices page.
Next week I'll go ahead and create such a page on our Wiki [1], and link it into the left nav bar on [2], unless there are objections. [1] https://cwiki.apache.org/confluence/display/CTAKES/ [2] http://ctakes.apache.org/ -- James -----Original Message----- From: notifications-return-634-Masanz.James=mayo....@ctakes.apache.org [mailto:notifications-return-634-Masanz.James=mayo....@ctakes.apache.org] On Behalf Of Pei Chen (JIRA) Sent: Friday, June 14, 2013 1:42 PM To: ctakes-notificati...@incubator.apache.org Subject: [jira] [Created] (CTAKES-210) Allow loading of Resources from InputStream instead of physical File Pei Chen created CTAKES-210: ------------------------------- Summary: Allow loading of Resources from InputStream instead of physical File Key: CTAKES-210 URL: https://issues.apache.org/jira/browse/CTAKES-210 Project: cTAKES Issue Type: Improvement Components: ctakes-core Affects Versions: 3.0-incubating Reporter: Pei Chen Priority: Minor Fix For: 3.1 File or Url.getRawPath() became problematic if they are read in from the jars from the classpath and which couldn't resolve to a physical File. a. Suggestion: Wherever possible, replace loading of resouces via java.io.File with InputStream instead. . We can add a new method in the FileLocator util and deprecate the old File method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
