[
https://issues.apache.org/jira/browse/UIMA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708396#comment-13708396
]
Peter Klügl commented on UIMA-2528:
-----------------------------------
Summary of the conversation on dltk-dev with Alexey Panchenko:
DLTK indexing thread should not execute UI code at all, that's the problem.
Could you check that UI and non-UI code is properly separated?
I can give a look at the sources if you provide the link.
...
It looks like all the code is contained in the single plugin project.
You'd better split the code into UI and non-UI projects, it's the most reliable
way of solving this issue.
...
Right. If modularized correctly, then it's physically not possible :-)
What happens in this particular case: indexer is in the dltk.core (non-UI) and
is started earlier. It tries to read some preferences, which are supposed to be
in the core part of your IDE. Unfortunately, there is only one module, which
includes UI, so deadlock happens.
There could be other similar cases.
> Open CAS Editor blocks eclipse start
> ------------------------------------
>
> Key: UIMA-2528
> URL: https://issues.apache.org/jira/browse/UIMA-2528
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor, ruta
> Affects Versions: 2.4.0SDK, 2.0.0TextMarker
> Reporter: Peter Klügl
> Fix For: 2.0.2ruta
>
> Attachments: jstack_ouput.txt
>
>
> I often observe that my Eclipse does not start, if the workspace was left
> with an open CAS Editor. This happens when I run an Eclipse application from
> a workspace with the CAS Editor and Ruta bundles. In order to get a working
> Eclipse, I have to deactivate the CAS Editor bundles, open the Eclipse, close
> the editors, close the Eclipse, and then activate the CAS Editor bundles
> again.
--
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
