Re: Getting back into it

my bad its jakarta.apache.org/turbine/maven

Andrew C. Oliver wrote:
> I really recommend Mavenizing to this effect.  I bet dion would help 
> with that..  (http://jakarta.apache.org/maven)
> 
> Alternatively (and this is what POI does) if maven doesn't do what you 
> need Centipede (http://krysalis.org/centipede) and Forrest 
> (http://xml.apache.org/forrest) might help.
> 
> However it really depends on whether Maven works under gump...
> 
> Gump should be one of our top priorities (jakarta.apache.org/gump) 
> because it could do the builds and site publish for us...
> 
> -Andy
> 
> Howard M. Lewis Ship wrote:
> 
>> Part of what you discuss may involve having multiple Tapestry 
>> modules.  Not good or bad, just a statement.
>>  
>> Yes, and we may need to reorganize things further to reflect the 
>> standard Apache project layout ... if we want to get the synnergy 
>> thing going, we want to make Tapestry "friendly" to other Apache 
>> developers.
>>  
>> Renaming packages looks like a big delete-and-add to CVS, so that's a 
>> good time to also reorganize directory structure.  We should 
>> brainstorm what that structure should look like.
>>
>>     ----- Original Message -----
>>     *From:* Geoff Longman <mailto:glongman-JVFTG6EM2JjNybAxKxMg8VaTQe2KTcn/@public.gmane.org>
>>     *To:* Tapestry Contrib 
>> <mailto:tapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
>>     *Cc:* [email protected]
>>     <mailto:[email protected]>
>>     *Sent:* Sunday, January 12, 2003 11:34 AM
>>     *Subject:* [Tapestry-contrib] Getting back into it
>>
>>     Whoo-ee, I have to say that this past holiday season was the worst
>>     on record for me.
>>     Just before Christmas good friends of ours had a terrible accident
>>     and their little girl was quite badly burned.
>>     It'll be a tough road ahead for their family but everything is
>>     relatively ok now.
>>          Also, I had a bit of a health scare myself last week and on 
>> top of
>>     all that we have a baby due imminently.
>>     Note: having a baby ids a good thing, it just added to the overall
>>     stress this holiday season!
>>          So, forgive if I've been quite the last while. I'm easing 
>> back into
>>     the 'normal' things now...
>>          Glad to see that the Apache thing is rolling along. Kudos to 
>> Andy et al!
>>          Looking for something to do Tapestry-wise and I was wondering if
>>     anybody had any thoughts on
>>     the structure for the code base in CVS.
>>          Currently, everything is located under the top-level Tapestry
>>     folder. That incl the framework, vlib, clover, contrib, workbench,
>>     and the
>>     mock opera :-) that Howard has built for testing.
>>          Would it make sense, after the move, the package rename, the 
>> Gump
>>     build (don't really understand that) was done
>>     if we examined the structure and split some of it out to the top 
>> level?
>>          The current advantage is that one can check out 'Tapestry' 
>> and get
>>     everything at once. One disadvantage is that to examine, for
>>     example, the vlib using Spindle is quite difficult.
>>          As I said, I realize there's still a lot of work to do before 
>> making
>>     these kind of changes. But I'm willing to play around with this.
>>          Geoff
>>          Geoffrey Longman
>>     Intelligent Works Inc.
>>          
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Tapestry-contrib mailing list
> Tapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/tapestry-contrib
> 





-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com