Pei,
Both CPE and CVD complain at load time when I remove the
'analysis_engine' from the resource path.
Caused by: org.apache.uima.resource.ResourceInitializationException: Could not
access the resource data at file:ProductionPostSentenceAggregate_step1.xml.
at
org.apache.uima.resource.impl.DataResource_impl.initialize(DataResource_impl.java:127)
at
org.apache.uima.util.SimpleResourceFactory.produceResource(SimpleResourceFactory.java:123)
Can I use the pom.xml or other properties file to find the resource in this
location?
Thanks,
~Sean
-----Original Message-----
From: ctakes-notifications-return-162-Murphy.Sean=mayo....@incubator.apache.org
[mailto:ctakes-notifications-return-162-Murphy.Sean=mayo....@incubator.apache.org]
On Behalf Of Sean (JIRA)
Sent: Thursday, December 06, 2012 3:13 PM
To: [email protected]
Subject: [jira] [Commented] (CTAKES-101) Term spotting pipelines returning
'unknown' classifications
[
https://issues.apache.org/jira/browse/CTAKES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512122#comment-13512122
]
Sean commented on CTAKES-101:
-----------------------------
Let me try that. Thanks.
> Term spotting pipelines returning 'unknown' classifications
> -----------------------------------------------------------
>
> Key: CTAKES-101
> URL: https://issues.apache.org/jira/browse/CTAKES-101
> Project: cTAKES
> Issue Type: Bug
> Components: ctakes-drug-ner, ctakes-pad-term-spotter,
> ctakes-smoking-status
> Affects Versions: 2.6-incubating, 3.0-incubating
> Environment: Linux and Windows OS
> Reporter: Sean
> Labels: patch
> Fix For: 2.6-incubating, 3.0-incubating
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The problem seems to have stemmed from the reorganization of the path
> structures with the latest cTAKES release. Due to time and resource
> constraints we were not able to test each project independently. This will
> be fixed in current and future releases.
--
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
