Log4j (which was the basis for log4net) has not been updated for years. There are other alternatives from the same author (slf4j and logback) and others, but log4j is still used by many, many viable ones. This is not dead, it just got to the point that there was nothing more real for it. Nothing that justifies the job or interferes with compatibility. When this happens with a commercial project, the company must invent a whole different goal for the product or do something else, and the product really dies. In open source, actually.
By comparison, JUnit has not been built for many years. Then Java got annotations, JUnit got competition (TestNG), and it suddenly moves again. Now, the original developers may not be in each case, but then the project will be branched or adapted. For example, TestNG allowed a smooth migration path from JUnit.
So, in the bottom line, if it is popular and used, it will not die on you.
Yishai Nov 02 '09 at 22:17 2009-11-02 22:17
source share