struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rich Feit <>
Subject Re: Struts Ti / JSF sample
Date Fri, 02 Sep 2005 04:57:12 GMT
First, I just want to mention that I've never been involved in a project 
where anyone's given so much thought/attention to the build from the 
ground up.  Thank you -- it's a pleasure!  Much nicer than rewriting the 
build a few months down the road.

I definitely support getting nightlies out there ASAP, for people to 
play with.  Is it legitimate to publish a directory 'sandbox/ti/nightly' 
under, or is that really off-limits while this project 
is in the sandbox?


James Mitchell wrote:

> I think it would be a good idea for us to discuss and decide on the  
> layout and build processes.  The build process needs to be documented  
> end to end.  We should identify the artifacts created, when and why  
> it is created.  More than the simple comments that I put in  
> maven.xml.  I will volunteer to do all of this work.
> As far as using Maven, I really like what we have so far.  It is  
> clean and efficient, but more work needs to be done.  Keeping the  
> build and layout organized is a team effort.  And I'm willing to do  
> all the work to keep it up to date.
> We were asked a few days ago, and I was hoping to do it, but time got  
> away from me.  When can we talk about putting nightlies together for  
> people to try out?
> -- 
> James Mitchell
> Software Engineer / Open Source Evangelist
> Consulting / Mentoring / Freelance
> EdgeTech, Inc.
> 678.910.8017
> AIM:   jmitchtx
> Yahoo: jmitchtx
> MSN:
> Skype: callto://jmitchtx
> On Sep 1, 2005, at 4:32 AM, Rich Feit wrote:
>> Hi all,
>> I've added a patch ( 
>> id=36454) for a sample that demonstrates using JSF as the view  layer 
>> for a Ti app.  It's a straight port of the Beehive/JSF  sample.  It 
>> doesn't necessarily show off JSF (or JSF best  practices), but it 
>> does demonstrate the integration (e.g., JSF  pages raising actions in 
>> Ti).
>> Our samples do beg the question(s):
>>    - Should we be building a 'normal' webapp for each one,  including 
>> an ant script that will build the app?  Something to put  into our 
>> distribution.
>>    - Should we use maven to build the samples .wars only for  
>> internal testing and perhaps for publishing the samples to a live  site?
>> I think we shouldn't require our users to have maven in order to  
>> build *projects* (not our source tree).  Is that reasonable, or am  I 
>> living in the past?
>> James - let me know if this blows up your maven structure in any  
>> way.  It seems to work, but I'm not trying to do anything from the  
>> top level.
>> Thanks,
>> Rich
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message