RE: [Proposal] Addition of Avalon# under Containers in Avalon sit e

["Farr, Aaron" <Aa...@am.sony.com>]

> -----Original Message-----
> From: Hamilton Verissimo de Oliveira (Engenharia - SPO)
> [mailto:hamilton.oliveira@agenciaclick.com.br]
> Sent: Monday, January 19, 2004 1:02 PM
> To: Avalon Developers List
> Subject: Re: [Proposal] Addition of Avalon# under Containers in Avalon sit
> e
> 
> -----Mensagem original-----
> De: Stephen McConnell [mailto:mcconnell@apache.org]
> 
> > +1 here as well
> >
> > On the subject - maybe we need to structure the content so that it is
> > clear that this is not just another container - but instead a language
> > specific implementation - which suggests we do a little breakdown to
> > show Avalon Java Solution as a group and Avalon# solutions as another.
> 
> I think you're right, but this time the Avalon# is minor part of all
> Avalon.
> So I propose that initially we expose it as another container instead.
> 
> Btw should I start a vote before changing the site?
>

Site changes are usually done via lazy consensus.  If we were completely
redoing the site (as suggested above), then yes, a preview version and vote
should be done first.

And I agree that at some point we might want to reorganize the site to more
prominently show the Java Solution vs Avalon# solution, but for now, let's
just put it under containers (or framework).

> 1. make sure your using maven beta-10
> 2. checkout avalon-site
> 3. edit avalon-site/xdocs/product/containers/index.xml
> 4. invoke maven  ("maven site:generate")
> 5. look in target/docs for the result

6. Import or move results to avalon-site/site
7. Commit changes to both xdocs and site sections.

avalon-site/site contains the finished site.  Whatever is in this directory
ends up live.

J. Aaron Farr
  SONY ELECTRONICS
  DDP-CIM
  (724) 696-7653


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org