Gary, If someone manages to have **both** log4j-1.2.17.jar **and** log4j-1.2.18.jar on the same classpath, nothing can help them. Really. Binary compatibility can't heal that.
Even if 1.2.18 was fully binary compatible, adding both jars to the classpath would blow the system anyway. In other words, I suggest the following message for NTEventLogAppender users: "sorry, if you use NTEventLogAppender you might have to skip 1.2.18 version or replace NT appender with others" We can't make 100% of the planet happy. For instance, I am sure releasing 1.2.18 makes the log4j2 team greatly unhappy no matter what. If we weigh "spend months on trying to build, sign and test NTEventLogAppender" vs "release 1.2.18 and say sorry to NTEventLogAppender users", I would go for dropping NT* (at least, as a temporary solution). Vladimir
