RE: Location of incubated downloads?

[Howard M. Lewis Ship]

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 place.
3) Copy build.properties into place (identifies locations of other LPGL
frameworks, including Jetty and JBoss).
4) Build using Ant

In reality, I do perform a build using exactly one command; I have a
meta-Ant build script that performs the four steps above.

I suspect that getting Tapestry working with Maven would not be difficult;
assuming Maven (or is it Gump) can download (and potentially unpack) the
necessary libraries and distributions and then use Ant to build Tapestry.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry



> -Original Message-
> From: robert burrell donkin [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, March 02, 2003 6:13 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Location of incubated downloads?
> 
> 
> hi howard
> 
> i'm working on a 'how-to' document along these lines for 
> jakarta-commons 
> releases at the moment. using the mirroring is just a little 
> involved. you 
> also need an account on daedelus.
> 
> if tapestry is now in the apache CVS and the release is 
> tagged, i could 
> probably reroll the release, sign, setup the required directories and 
> upload if you like. alternatively, you could wait until i've 
> finished the 
> documentation (and run it past infrastructure) and use that.
> 
> i suppose that this also raises a more general question about how the 
> incubator should handle releases. it might be better if 
> releases from the 
> incubator were managed by the project but executed by the 
> incubator team.
> 
> - robert
> 
> On Saturday, March 1, 2003, at 05:16 PM, Howard M. Lewis Ship wrote:
> 
> > We are already aware of this and OF COURSE, we would prefer 
> that our 
> > Tapestry distros be hosted on Jakarta. I would vastly prefer this.
> > Perhaps
> > you are willing to update the Wiki with the necessary procedures for
> > accomplishing this?
> >
> > I've been trying to gradually shift over Tapestry from SF 
> to Jakarta.  
> > I' d prefer to go slower, and leave things behind on SF 
> longer, rather 
> > than make
> > too many waves at Jakarta.  I don't want the Tapestry user 
> community to go
> > through too much pain (i..e, switching mailing lists 
> multiple times, or
> > switching bug systems multiple times).
> >
> >
> > --
> > Howard M. Lewis Ship
> > Creator, Tapestry: Java Web Components 
> > http://jakarta.apache.org/proposals/tapestry
> >
> >
> >
> >> -Original Message-
> >> From: Justin Erenkrantz [mailto:[EMAIL PROTECTED]
> >> Sent: Saturday, March 01, 2003 11:48 AM
> >> To: [EMAIL PROTECTED]
> >> Subject: Location of incubated downloads?
> >>
> >>
> >> 
> >>
> >> 27 February 2003 - Tapestry 2.3 Released
> >>
> >> The first full release of Tapestry hosted at Jakarta is here . 
> >> Tapestry 2.3 is a modest improvement on 2.2, fixing 
> several bugs and 
> >> adding a few new capabilities and components.  Work is 
> well underway 
> >> on the much more ambitious
> >> 2.4.
> >>
> >> where the 'here' link is:
> >>
> > 
> >
> > -/-
> >
> > Can someone from the incubator (whoever is responsible) 
> please relay 
> > to
> > the
> > Tapestry folks (don't know who they are) that releases 
> should only be
> > occurring using the ASF server infrastructure.  Perhaps 
> this needs to be
> > made
> > clearer to new projects.  -- justin
> >
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Location of incubated downloads?

[dion]

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 Tapestry is a manual process:
> 1) Get latest snapshot from CVS
> 2) Copy external distributions (several LGPL libraries needed at compile
> time) into place.
> 3) Copy build.properties into place (identifies locations of other LPGL
> frameworks, including Jetty and JBoss).
> 4) Build using Ant
> 
> In reality, I do perform a build using exactly one command; I have a
> meta-Ant build script that performs the four steps above.
> 
> I suspect that getting Tapestry working with Maven would not be 
difficult;
> assuming Maven (or is it Gump) can download (and potentially unpack) the
> necessary libraries and distributions and then use Ant to build 
Tapestry.

Maven can do the above. But there are probably easier ways of doing it.

How many 'deliverables' are there from the ant build? Is it just one 
tapestry jar file, or are there other things produced as part of the 
build.

I'll check tapestry out of cvs and see what I can do to help.
--
dIon Gillard, Multitask Consulting
Blog:  http://www.freeroller.net/page/dion/Weblog
Work:  http://www.multitask.com.au




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[STATUS] Tapestry [LACK-OF] Progress

[Howard M. Lewis Ship]

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 procedures for getting things done.  Nothing
is documented.  Simple things like the correct way to distribute a release
(including signing and mirroring) are just "known" by the right people ...
and I don't even know who is in the know.

Andrew and Dion have been helpful, both before the move and after.

The only other accomplishment of the incubation process has been a code
audit that resulted in a shuffling of the libraries checked into CVS and
distributed with the framework.

Jakarta infrastructure is non-existent. Worse, the Jakarta culture
erroneously expects things to get done based on e-mails, rather than
something organized, like using BugZilla to track infrastructure requests. 

The Incubator team has yet to provide a time table or a check list to
indicate what the exit criteria are.  In terms of Tapestry's commitments to
the Incubator, it looks like we're more than there (based on
http://incubator.apache.org/process.html).  In terms of Incubator's
commitments to Tapestry ... that is, to assist Tapestry in moving into
Jakarta, fitting in, and accessing infrastructure; very little has been
accomplished.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Incubator DOA (Re: [STATUS] Tapestry [LACK-OF] Progress)

[Jeff Turner]

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 stating the blindingly obvious.  Is it just me?


--Jeff

On Mon, Mar 10, 2003 at 06:58:22PM -0500, Howard M. Lewis Ship wrote:
> 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 procedures for getting things done.  Nothing
> is documented.  Simple things like the correct way to distribute a release
> (including signing and mirroring) are just "known" by the right people ...
> and I don't even know who is in the know.
> 
> Andrew and Dion have been helpful, both before the move and after.
> 
> The only other accomplishment of the incubation process has been a code
> audit that resulted in a shuffling of the libraries checked into CVS and
> distributed with the framework.
> 
> Jakarta infrastructure is non-existent. Worse, the Jakarta culture
> erroneously expects things to get done based on e-mails, rather than
> something organized, like using BugZilla to track infrastructure requests. 
> 
> The Incubator team has yet to provide a time table or a check list to
> indicate what the exit criteria are.  In terms of Tapestry's commitments to
> the Incubator, it looks like we're more than there (based on
> http://incubator.apache.org/process.html).  In terms of Incubator's
> commitments to Tapestry ... that is, to assist Tapestry in moving into
> Jakarta, fitting in, and accessing infrastructure; very little has been
> accomplished.
> 
> --
> Howard M. Lewis Ship
> Creator, Tapestry: Java Web Components
> http://jakarta.apache.org/proposals/tapestry

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Incubator DOA (Re: [STATUS] Tapestry [LACK-OF] Progress)

[Conor MacNeill]

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 to Jakarta
> without being further jerked around.
>
> I feel I'm stating the blindingly obvious.  Is it just me?
>

Jeff,

I agree that incubator is currently failing. Whether it was flawed from the 
start, I'm not really sure. IMHO, incubation won't work unless the incubator 
project can spare the time to help projects incubate. 

With respect to Tapestry, I agree. I think the incubator PMC should perhaps 
vote to promote it into Jakarta. The current limbo is not fair to the people 
involved.

Conor


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]