Please keep me posted on this documentation.
Tapestry is not (yet) under Maven and I haven't had time to research how to
integrate the two. Building Tapestry is a manual process:
1) Get latest snapshot from CVS
2) Copy external distributions (several LGPL libraries needed at compile
time) into pl
This belongs more on tapestry-dev, so I've copied it there.
"Howard M. Lewis Ship" <[EMAIL PROTECTED]> wrote on 11/03/2003 10:32:35 AM:
> Please keep me posted on this documentation.
>
> Tapestry is not (yet) under Maven and I haven't had time to research how
to
> integrate the two. Building T
How, exactly, is Tapestry ever expected to exit the proposal stage?
Despite repeated attempts, Tapestry is NOT in BugZilla. We're still forced
to use SourceForge for bug tracking.
Tapestry's mailing lists are not getting archived any more (not since 2/21).
Nobody seems to know ANY of the proced
Feh.
Incubation was a dumb idea from the start. It is busy failing in
practice.
PMCs should manage the acceptance of new subprojects, not some
disinterested Incubator PMC.
IMHO, scrap this failed experiment and let Tapestry migrate to Jakarta
without being further jerked around.
I feel I'm sta
On Tue, 11 Mar 2003 04:04 pm, Jeff Turner wrote:
> Feh.
>
> Incubation was a dumb idea from the start. It is busy failing in
> practice.
>
> PMCs should manage the acceptance of new subprojects, not some
> disinterested Incubator PMC.
>
> IMHO, scrap this failed experiment and let Tapestry migrate
