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? > >> > >> > >> <http://jakarta.apache.org/site/news.html#20030227.1> > >> > >> 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: > >> > > <http://sourceforge.net/project/showfiles.php?group_id=4754> > > > > -/- > > > > 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]
