Most of the info about this I put in this thread: http://communities.vmware.com/thread/115466
Wednesday, January 30, 2008
Monday, January 14, 2008
Read this forum entry I wrote about what could be a common NSIS coding mistake with macros. For instance, this code:
IfErrors 0 +2
!insertmacro LogProgressMessage '"There was an error..."'
will likely cause the error "Installer corrupted: invalid opcode" at runtime. Instead of using +2, you should use a label.
Tuesday, January 1, 2008
Just filed a bug against log4j; it can swallow InterruptedException delivered to a thread that uses logging. This is because it catches IOException and ignores it, but IOException can also be InterruptedIOException, which can be generated on some platforms when a thread is interrupted.
Update: As of 8/14/2008, the log4j developer Curt Arnold has bug 44157 fixed, and the current plan is to ship the fix with log4j 1.2.16.