Vincent Massol wrote: > What do you mean by source ? Only the java files or the full tree, > including build, conf, etc ?
Everything, just as it stands. > Well, it shows how to package a scaffold application and how to unit > test one which is not that bad after all ... :-) Sorry, didn't notice the unit tests. It just looked like the blank application with the scaffold.jar thrown int. > Hey, I'm not saying I'm right here ... ;-). I'm trying to understand > the motivation behind packaging scaffold as a war ... > > I find it troubling to deliver a library as a WAR when what we want to > deliver is actually a jar. However, it is also very important to always > deliver a sample application for any library, which shows how to use it > and a war fits nicely for this. I guess I'm thinking that the Scaffold "application" could be the documentation and unit tests, which would also serve as a sample application. To use Scaffold in their own application, they can just pull out the JAR, or download the JAR directly from distribution folder. (As is being discussed on General.) We might also consider an alternative target in the build that created a blank application, but with the unit tests (since every application should have unit tests!), that they could build, and then rename for their own application. Rather like the struts-blank, except that you just build and new one and rename it, rather than copy and rename. Perhaps there could be some settings in the build.xml that also customized some of the files for the new blank application? -- Ted Husted, Husted dot Com, Fairport NY USA. -- Building Java web applications with Struts. -- Tel +1 585 737-3463. -- Web http://www.husted.com/struts/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
