incubator-ctakes-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Miller <>
Subject Re: [jira] [Created] (CTAKES-170) relation extractor has dependency on clinical pipeilne
Date Fri, 22 Feb 2013 20:28:51 GMT
Sorry James for committing this so quickly, I thought the original 
direction was an oversight so just fixed it without discussion.

I made a dependency graph with pen and paper this morning when maven was 
complaining about a dependency cycle.  My takeaway was that 
relation-extractor was somehow screwing everything up by being the only 
component pointing the way it was pointing.

Is it ok to leave the fix for now, and pending the results of discussion 
on 165 go change it back if necessary later?


On 02/22/2013 03:18 PM, Masanz, James J. wrote:
> I disagree. Or I should say that it should depend on what the outcome of CTAKES-165 is.
> It is necessary and I think it is the right direction right now.
> Maybe clinical-pipeline should have been called basic-ner or something.... seems to be
a source of confusion now. but I digress.
> -- James
>> -----Original Message-----
>> From: ctakes-notifications-return-409-
>> [mailto:ctakes-notifications-
>>] On Behalf Of Tim
>> Miller (JIRA)
>> Sent: Friday, February 22, 2013 2:14 PM
>> To:
>> Subject: [jira] [Created] (CTAKES-170) relation extractor has dependency
>> on clinical pipeilne
>> Tim Miller created CTAKES-170:
>> ---------------------------------
>>               Summary: relation extractor has dependency on clinical
>> pipeilne
>>                   Key: CTAKES-170
>>                   URL:
>>               Project: cTAKES
>>            Issue Type: Bug
>>              Reporter: Tim Miller
>>              Assignee: Dmitriy Dligach
>>              Priority: Minor
>> dependency should go in the other direction if it is necessary at all.
>> --
>> 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:

View raw message