forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Portier <>
Subject Re: Where goes Forrestbot?
Date Mon, 14 Oct 2002 21:17:34 GMT
briliant insight.

we just need to elaborate some more on how (from a users 
standpoint) the bot should be working
(nice to be back by the way: this week is catchup-read week, next 
week is again loaded with other work, after that I'ld like to 
speed up to get some of this into the forthcoming 0.2 that was 
mentioned: any real plan and list of things to get in? a target 

As a kind of requirements gathering up front what is it that 
bot-users (any around?) would like/need to do?

- build the bot-distribution
- set it up to work in a cron (good idea to provide more then 
just docs)
- add/remove/get-list of projects to process (I'ld prefer 
seperate files in dirs over the current all holding project-conf)
- have intermediate runs (without deploy) to test
- others?

at this moment I have the feeling people would want to have some 
hierarchical organization to things: first level would decide 
where to deploy to and then group on a second level all the 
projects that should be put next to each other on that same 
location, also setting some overriding properties in those 

what about centrally overriding properties set for each specific 
project (like skin)?

still catching on the read... for the stuff we don't override we 
need to fallback on the project-settings: what happened to 
siteplan? (as an idea, not the file) is everything now in

what if the project's ant target to forrest is dependend on other 
tasks? (how is the link to gump/vindigo/centipede/whatever nowadays?)

more emotions/thoughts?

Jeff Turner wrote:
> Hi,
> The 'bot' target is currently in build.xml. This means it isn't visible
> to external projects. build.xml isn't the right place for it anyway, as
> it is intended only for Forrest-specific build targets. The question is,
> where should it go?
> I think it would be a good idea to create a separate distribution for
> the Forrestbot. The notion of 'distributions' was introduced when
> was split off from build.xml. Each distribution is
> "Forrest packaged for a separate user group". So we'd have:
> shbat      # Forrest for individual project developers
> maven      # Forrest for Maven users (a Maven plugin)
> centipede  # Forrest for Centipede users (Centipede cent)
> forrestbot # Forrest for site integrators and deployers
> So when developing a site, you'd use the 'shbat' distribution. Then on
> the server, you'd use the 'forrestbot' distribution.
> Each distribution can now evolve specifically for it's user group. The
> forrestbot distribution could come with preconfigured crontab files.
> shbat users don't need to see or worry about forrestbot.conf.xml files.
> Thoughts?
> --Jeff

Marc Portier                  
Outerthought - Open Source, Java & XML Competence Support Center                    

View raw message