Hi, We still have this one open:
http://josm.openstreetmap.de/ticket/4861 Today there was another report of basically the same problem http://josm.openstreetmap.de/ticket/4942 For me it happened frequently on upload of large data sets (with active filters). This can be a little disturbing so I reduced the exception to a warning on the console in [3202]. But it is really an error that leads to iteration over "old" members of the collection, potentially creating other problems. The current state is acceptable because the only situation where the problems arises is on update of the filter flags. It does not matter so much if one or two updates are missed under quite rare circumstances. (But if an exception is thrown, it breaks the upload process and stuff like that.) I suggest, we update tested again to include [3202], then continue with the new development cycle, but try to find a proper fix for this asap. These thread things give me a headache :) , any suggestions welcome! __ Sebastian Dirk Stöcker wrote: > Hello, > >>> If no bigger problems are reported till friday, then new development cycle >>> may start at friday and we move to Java6. >> Actually we have a critical bug: #4929 - filtered objects are selectable. >> This should be fixed soon. > > I increased tested to 3201. The main development cycle is opened again. > Please try to check in more mature new code compared to the time before. I > don't want to have such a long stabilizing phase again. > > It is fine to have new features, but the way how these are implemented > greatly influences the number of resulting bug reports. Some more care > is required. > > Special thanks to Sebastian and Jiri, who did a great job to improve the > quality in the last weeks. > > Also JOSM is now open to Java6. As soon as the first JAVA6 code is > really checked it, the author should make an announcement in the > StartupPage. _______________________________________________ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev