Wow. I expected people to complain about this, but I didn't think it would be in less than a day. See https://issues.apache.org/jira/browse/THRIFT-416 for some context.
Java doesn't support a preprocessor, so I don't think there is any way to optionally eliminate the log4j dependency. We could use slf4j, but that would just create the same problem. We could switch back to java.util.logging. I don't think it makes sense to put log4j into our source repository, but we could possibly put it into the release tarball (and instant releases) if the Java guys can come up with a plan for it. --David Michael Stockton wrote: > I tried to build thrift this afternoon and failed because I don't have > log4j on my machine. This seems to be a bit unfriendly at the moment > and to me feels like a 0.1 blocker-type issue. How many people will > give up on thrift if make fails? Can we bundle log4j with thrift or > find a better way to fail? > > Michael
