Peter Donald wrote:
>
> Hi,
>
> Just to make you aware a lot of projects use "build" to signify the
> intermediate files and thus using build may be unwise. I would also
> recomend using
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.
>
> tools/bin/ for tool related scipts
> tools/lib/ for tool related jars
>
> and instead of having scripts at top of directory structure just have a
> build.xml and maybe build.[sh|bat] to wrap around ant.
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.
>
> At 07:34 31/3/01 -0500, Geir Magnusson Jr. wrote:
> ><aside>
> >I want to note that I think having each component under the same CVS
> >tree will be ungainly as we acquire more components. It will be
> >important to be able to download individual nightly builds of each
> >component, as well as the whole thing...
> ></aside>
>
> gump has entries for the j2eeunit component and can easily be switched to
> nightly build mode. I would recomend that anyone who wants gumping/nightly
> builds contact Sam/Alexandria with details.
I wasn't thinking about Gump here (I just assumed that we would get Gump
to test rigorously...)
By nightly builds, I misspoke - I meant snapshot. We should be able to
offer the nightly snapshot of each component if you want to just focus
on one piece, and not have to drag the entire thing down when it gets
big with all those great projects that are pouring in.
;)
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
