[
https://issues.apache.org/jira/browse/GROOVY-7570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Endre Stølsvik updated GROOVY-7570:
-----------------------------------
Attachment: Error Log - Event Details - Session Data.png
> Eclipse: Upon save of editor: "Save Failed" "assertion failed:"
> ---------------------------------------------------------------
>
> Key: GROOVY-7570
> URL: https://issues.apache.org/jira/browse/GROOVY-7570
> Project: Groovy
> Issue Type: Bug
> Reporter: Endre Stølsvik
> Attachments: After it has happened - notice still modified
> asterix.png, Error Log - Event Details - Session Data.png, Save All Failed -
> assertion failed.png, Trying to close failed editor makes the Save Resource
> dialog appear.png
>
>
> Way too often when I have changed some code in a file, and then hits Ctrl+S,
> a small popup comes up, titled "Problem Occurred", stating two lines of text:
> "Save Failed" "assertion failed:", with two buttons "OK" and "Details >>".
> Clicking Details does not help, it just repeats the four words of text.
> You then have to say "OK", and the contents of the file window disappears,
> being replaced by a single blue line with the text "Error" below. You do not
> have any way whatsoever to recover your changes.
> When you finally accept your fate once again, and try to close the window,
> the normal "Save Resource - file has been modified, save changes?"-popup
> comes up. But the "Save"-button just pops the error popup up again (However,
> it now says "Save All Failed" instead of just "Save Failed"). So the only
> thing you can do, is to hit "No".
> You are left with having to Ctrl+S all the time, as if you were writing in
> some old version of Word - constantly being terrified of your work being
> destroyed at any time, of course not keeping a complete "changelog" in your
> head, so you are always left a bit in the dark when it finally happens again.
> There is no stable pattern I to this that I have managed to deduce, but maybe
> it happens more often when modifying inside the JavaDocs?? I do not know, as
> I do not hit ctrl+S all the time. Also, one do get a feeling that lots of
> Ctrl+S keeps the problem slightly away. (The Groovy Eclipse editor is pretty
> crazy, only being correctly colorized and analyzed right after a Ctrl+S,
> otherwise just a single extra letter will make colorizations and underlinings
> etc move off..)
> (Hopefully needless to say, this is so hellishly frustrating that it is very
> hard to write this bug report in any civilized tone.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
