Gary>If you manage your Maven (for example) POM properly, Gary>and you assemble a distribution you'll only end up with the latest version.
Then I don't truly understand what did you mean by mentioning "Jar hell". I claim that removal of NTEventLogAppender can't cause "jar hell" because people either keep using 1.2.17 or upgrade to 1.2.18. You said: "We cannot break binary compatibility, that would create a bigger mess: Jar hell" What I say is that if people end up with *both* 1.2.17 and 1.2.18 on the classpath (e.g. failing to manually replace jars in all the places), they would be screwed no matter how we try keep the compatibility. That is why removing a rarely used class is not a showstopper. All in all, it looks like Leo has already fixed the compilation of the native code, so the discussion of "removal NTEventLogAppender" is not that important. Vladimir
