Library has changed: bug has reappeared

[AEgit]

JabRef 5.0-alpha--2019-12-11--c3b7ee7
Windows 10 10.0 amd64
Java 13.0.1

1. Open JabRef database
2. Make no changes at all to the database
3. Try to close the database
4. Message: "Library has changed" appears giving the option to "Save changes", "Discard changes", and "Return to JabRef"

I thought this issue had been solved in some previous contribution, but it appears again in the recent dev version of JabRef.

[AEgit]

Update: If I use a database that has been stored using the developer version of JabRef instead of the old version 3.8.2 the issue does not appear.

The issue therefore might (?) be related to the problems reported here #5735 (comment) and here #5734, especially considering the fact that some of the issues also appear to relate to the version in which the JabRef database was stored in (see updated descriptions in the issue reports).

If that is the case, this might explain also, why it previously had been impossible to reproduce similar error reports. Maybe, the underlying database had not been saved using the current dev version of JabRef, but an older (release) version of JabRef.

[Siedlerchr]

@AEgit It would be nice if you could send us your 3.8.2 db. Simply send it to developers@jabref.org if you don't want it to be public. When you open an older version in the new version, there are some migration steps happening, especially regarding groups.

[AEgit]

@Siedlerchr Done. Thank you very much for your help!

EDIT: Note, that the database saved with JabRef version 5.0 gives a warning message when you open the database:

I think this the respective lines contain open brackets, that are not closed as they should be. Note, however, that the same database originally saved with JabRef version 3.8.2 and then opened with JabRef 5.0 does not give these error messages. Therefore something must happen during the conversion from 3.8.2 to 5.0 that causes this problem.

The warning message is NOT (or at least should NOT be) related to the issues I mentioned here.

[tobiasdiez]

For the first time every, I was finally able to reproduce this error (with my own file). Let's see when I find the time to investigate this further...

[AEgit]

Note, that I cannot reproduce this behaviour with the following older development version:

JabRef 5.0-alpha--2019-12-04--5dcb565
Windows 10 10.0 amd64
Java 13.0.1

[Siedlerchr]

When running current master from Eclipse I don't get a change dialog even if I modify the file ony my disk. I hardly can trigger that dialog. Still not understanding it.

[koppor]

Refs #5257

[tobiasdiez]

This is essentially a duplicate of #4877