Peter Donald wrote:
>
> At 11:17 31/3/01 -0500, Geir Magnusson Jr. wrote:
> >Hm. Ok. There is a current 'best practices' suggestion for Jakarta,
> >and I was sticking to that. We do the same in Velocity, use 'build',
> >and that works out fine, but we are small in size and scope.
>
> All the ones that inherit from Jon's way use build/ for tools I believe and
> another set who inherited from another group use build/ for intermediate
> files. The best practices document has been amended to indicate these
> things ;)
>
Sounds good. I am not married to either way. Just want to avoid piling
everyting into the top level directory, make it consistant, and make it
easy having the basics lying around for all to use, and to keep users
from having to run around to find stuff just to see what something is
about.
> >Fundamentally, what I was hoping for is a build.sh/bat to wrap around
> >Ant - nothing more, other than also including Ant so it's easy to build.
>
> Also may want to include anakia/stylebook and junit because most projects
> will use that.
>
Yep - I mentioned Anakia and JUnit elsewhere, but I forgot stylebook.
+1 :)
For the 'no included jars' camp, would you also make the user go off to
find stylebook to make docs as well?
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
