Not that I blame anyone, because there was so little time recently for
developers to do all that was required, but distribution .zip seems quite
confusing. It seems more as plain CVS checkout made for developing, than as
proper distribution package for end users. There are bunch of unnecessary
directories, no dependency .jars at all (I thought there should be just few
with non-ASL licence missing) ...etc..
Some polishing definetly has to be done here.
Root directory with /docs, /lib, /src, IMPORTANT.txt (to inform about
missing dependencies) and build.xml for downloading missing dependencies
would be ideal.
-Vjeran
----- Original Message -----
From: "Kevin Menard" <[EMAIL PROTECTED]>
To: "Tapestry users" <[email protected]>
Cc: "Jakarta General List" <[email protected]>
Sent: Saturday, June 25, 2005 6:29 PM
Subject: Re: [ANNOUNCE] Tapestry 4.0-beta-1
Howard Lewis Ship wrote:
Tapestry is distributed as a combined binary/source distribution, and
a seperate documentation distribution.
What is required to build this? Am I correct in assuming the process is
like Tapestry 3.0, with non ASF libs being fetched by an ant script? If
so, what really is the procedure for getting this beta working?
Thanks,
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
