cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <>
Subject Re: excluding unstable blocks by default
Date Fri, 02 Apr 2004 17:27:55 GMT
Geoff Howard dijo:
> Quick comment on a busy day: I'd rather see us take this opportunity to
> allow/create build profiles.  The core cocoon-provided ones (core,
> all-stable,
> all-current, all (includes deprecated), "publishing", "dbapps"...) would
> be
> created out of gump.xml, but the user could then keep multiple options
> laying
> around simultaneously: client1.(build|blocks).propertes, or live, stage,
> etc.
> We'd create convenience task aliases for the stock ones as you mention
> below,
> and build custom would default to the, but you could also
> swap
> in a specific profile with -Dbuild.profile=client1 etc.
> I proposed the ant side of how this would work a few weeks ago in the "How
> can I
> help" thread.

Good idea. it is by far more functional for entry level users. Something
like a Linux distro: Database distro, web server distro, workstation
distro, etc. Really sound good to me.

Also for the "advanced users" we can also allow the "customize" option.

Best Regards,

Antonio Gallardo

View raw message