Splitting Up the Default /lib Directory
Came across an interesting idea in a directory structure for the examples in a Spring tutorial at Zabada Technologies. I’ve never seen it before, but it does solve a common problem I’ve had with mixing jars that were only needed for testing or things like the servlet-api.jar which would already be in any container.
The solution is simple. The main top level /lib directory just contains all the jars that are actually needed to run the app. Another top level /lib-build is just used for dependent jars like the servlet-api.jar and the junit.jar that would only be used for building.
Since I still haven’t looked into AppFuse and it’s directory structure I don’t know whether I’ll adopt this as a default for the team yet, but it is a nice simple solution. I just have to run it by our development practices committee, and convince them of the usefulness.
Ed Gibbs @ July 11, 2005
The easiest way to “check out” AppFuse is probably to watch these videos. If you have any questions, please send us some e-mails on the AppFuse Mailing List (subscribe by sending a blank e-mail to users-subscribe@appfuse.dev.java.net).