Comment 5 for bug 286288

I tried to reproduce this scenario with the current grokproject version. Thomas, can you confirm that this issue does not occur anymore with the most recent grokproject version? (I tested it with grokproject-1.0a2).