This was one of the earliest occasions when I really began to appreciate the fact that a complex, complicated design for some facility in a software or hardware product is usually not an indication of great skill and maturity on the part of the designer. Rather, it is typically evidence of lack of maturity, lack of insight, lack of understanding of the costs of complexity, and failure to see the problem in its larger context.
Why is it that, with all to many of us, the more familiar we are with sound Christian teaching the less Christ-like we become in our daily lives?
I remember being surprised the first time I heard that "maturing in the faith" was dangerous. Must run now, maybe more another time.
From the left: Andy Nourse, Mike Brown, Dave Scheifler (my supervisor), Peggy Doucette (our manager), two I cannot identify, and a fragment of Charlotte Richardson behind someone else I recognize yet cannot name.
I've been getting an InvocationTargetException while parsing my jocl file, but the error message never contains where the real problem occurs.Other reasons given explain why the error is misleading. But for the moment, make sure that the commons-collections JAR file is in the path as well.
…
1) The commons-pool package uses the commons-collections, but does not document that requirement in any of its documentation.
I encountered this running junit from an ant build, trying to get around a LinkageError problem by selectively adding JAR files to the classpath for testing. Turns out my version of ant might have been hosed, too, in some way, but that's another issue.
