> -----Original Message----- > From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]]
> > Until then, why not try the existing target to build the jar > w/o any of the other external packages?? no problem about that, my concern was just about the official release. It makes manager anxious when you tell them that you have to take an official release and hack it for various reasons and it adds overheads to the development environment setup. I prefer to have all necessary bricks available and get what I need than discovering later than something is surprisingly compiling without having the API 'officialy' in the classpath but simply because there is a version 'x' merged in a jar of another API. It gets better simply when someone is telling you 'I have problem sometimes' until you realize that you have a different version of the API in the webinf/lib and of course Tomcat does not guarantee the loading order :) Stephane -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
