[
https://issues.apache.org/jira/browse/UIMA-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510005#comment-13510005
]
Richard Eckart de Castilho commented on UIMA-2512:
--------------------------------------------------
I don't seem to have the problem with all type systems.
I created a new Java project in a new workspace and copied one of the type
systems were I have the problem to that new workspace (along with another type
system that it imports). In that new project, there is no problem.
In the workspace where I have the problem:
* it doesn't seem to make a different if the type system contains imports or not
* the dirty editor problem occurs only if I open the type system in the CDE,
when I open it in a text editor or XML editor, there is no problem
* the problem is absolutely reproducible with several file systems but only in
that workspace it seems
Any ideas what kind of information I could provide to pinpoint this? I suppose
the "easiest" would be to run the entire Eclipse in debug mode and connect to
it with a remote debugger...
> Type system editor always dirty
> -------------------------------
>
> Key: UIMA-2512
> URL: https://issues.apache.org/jira/browse/UIMA-2512
> Project: UIMA
> Issue Type: Bug
> Components: Eclipse plugins
> Reporter: Richard Eckart de Castilho
>
> Since some time (some 2.4.0-SNAPSHOT, still present with 2.4.1-SNAPSHOT),
> whenever I open a type descriptor in the CDE in Eclipse, the editor is
> immediately marked as dirty. If I save, the dirty mark dissapears very
> briefly, then is back. Whenever I close the editor, it asks me if I want to
> save first.
--
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
