[
https://issues.apache.org/jira/browse/CTAKES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510006#comment-13510006
]
Sean commented on CTAKES-101:
-----------------------------
Hello Pei,
I'm trying to test the fixes at the unit level as well as when built
via the maven package command. I'm new to maven so these are obviously newbie
type questions.
Is it a manual step, the pear installer, or some other means you use to
combined the project as they exist in the binary version you shipped (with the
bin, desc and resources all at the root install)? I see that zips/gz in the
ctakes-distribution project, but I wondering if you further process to ship.
Also, prior to bundling I would like to have the option to run at the
individual project level. Since the resources and descriptor files
dependencies are distributed do you leverage maven to consolidate them or
should I use the old standby of just updating the classpath?
Thanks,
~Sean
> 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-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
>
> 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
