> One potential caveat here is that you'll have a set of the JARs in the > WEB-INF directory of every such example ... that can be solved by > providing a post-install script that can assemble runnable WARs for > the examples from a single included copy of each jar.
Interesting idea. > No, that one makes sense. What doesn't make sense is to have hundreds > of copies of commons-beanutils.jar (or whatever) spread throughout the > source repository. Agreed. > (Note that I would make the same sort of argument against checking in > *any* generated artifacts, including Javadocs ... :-). Agreed. We currently use SVN to update the website (including javadoc.) My notion is that we should use Maven or some alternative publishing mechnasim for that. I agree that this stuff in SVN causes too many headaches. > Craig sean
