[osmosis-dev] [PATCH] --log-progress --buffer results in OsmosisRuntimeException: initialize has not been called

() in EntityProgressLogger.initialize(). Attached is a patch that I believe fixes this bug. -Richard From 33cabe82f3a55dba2f3f5942cbe021177a8db493 Mon Sep 17 00:00:00 2001 From: Richard Hansen rhan...@bbn.com Date: Sat, 14 Jan 2012 15:51:33 -0500 Subject: [PATCH] Add missing call

[osmosis-dev] calling DataPostbox.release() multiple times

Hi all, I believe I have found a bug in DataPostbox.release(). (I'm using git master, currently 43089ed.) According to the javadoc comments, Releaseable.release() can be called multiple times. However, DataPostbox.release() can only be called once. If it is called a second time, it

Re: [osmosis-dev] calling DataPostbox.release() multiple times

' boolean at the top and clear it at the end. Then EntityBuffer.release() would be modified to only call buffer.release() if outputThreadIsRunning is true. -Richard From 86c93d88e011ab76b79737c6185bd138f2eced76 Mon Sep 17 00:00:00 2001 From: Richard Hansen rhan...@bbn.com Date: Sun, 15 Jan 2012 15

[osmosis-dev] [PATCH] Remove changing=true from fixed-revision Ivy dependencies

In ivy.xml, the setting 'changing=true' tells Ivy that the dependency's jar might change despite its version not changing. This causes Ivy to always query the repository, even if the jar is available in the local cache. This setting is often used to express a dependency on the latest snapshot