Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 72.14.220.158 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=MUNXNKj5S5N9Gy9bb+v4MtVjXvCo4x+5nC8WB9Qgf53UpzJXtHMI1yud95tJqx+FYKCcZH26xWsyHemlMW8EFI2MLD0oHqilH+AEleYmmeRK5Ef2A6D1yTeYh+YVzY1dTd6dnw/s+qdzEUwAN6BqqLgJB/zsVvf5RcWHeC8LWp4=
Message-ID: <25aac9fc0712200619h2377aa58raa8e7b3f3e3a1720@mail.gmail.com>
Date: Thu, 20 Dec 2007 14:19:51 +0000
From: sebb <sebbaz@gmail.com>
To: "HttpComponents Project" <dev@hc.apache.org>
Subject: Re: [DISCUSS] future web site structure
In-Reply-To: <476A767E.30409@dubioso.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4762AB4B.6080807@dubioso.net> <1198083359.7175.23.camel@okhost>
	 <476A2815.3060307@dubioso.net> <1198157312.23673.15.camel@okhost>
	 <476A767E.30409@dubioso.net>

On 20/12/2007, Roland Weber <ossfwot@dubioso.net> wrote:
> Hi Oleg,
>
> >> I start to get the feeling that Maven is a black hole that
> >> drags everything into it.
> >
> > Maven is VERY invasive. It either its way or the highway. However, it
> > does help to enforce uniform release structure and process, which is, in
> > my opinion, a good thing.
>
> I'm fine with Maven as a _release_ build tool. I'm less fine
> with Maven as a site generation tool. I see the point as long
> as the site is published with the release, as is the case for
> commons-httpclient with it's extensive documentation. That's
> why I suggested to use Maven for the parts of the site that
> are associated with a component and usually updated only after
> a release, and use something else for the "main" site that
> could see intermediate updates. But even that won't work if
> we want to add documentation to a component and publish that
> without waiting for the next release.
>
> I just noticed that the HttpComponents site only uses Maven
> report plugins that are tied to the source code, which is
> good. The 3.1 site also generates reports from SVN, which
> makes little sense unless the site is updated on a regular
> basis.
> Would you mind me removing the "Change Log", "Developer Activity"
> and "File Activity" reports from the old site? Some others also
> make little sense, given the current change frequency in the
> 3.1 codebase: "JavaDoc Report", "JavaDoc Warnings Report", and
> "Task List". But maybe you are using these locally when coding?
>
> > Roland, Sebastian
> >
> > Feel free to explore alternatives. I will happily step aside for a
> > while.
>
> I don't have a short-term alternative that supports a friendly
> wiki-like text markup. I'm beginning to think that it isn't
> such a bad idea to have a site published from a Confluence Wiki
> though.
> Go ahead with Maven site building. We can consider alternatives
> next year, when the dust has settled. I'll find enough to do to
> keep me occupied.

+1, ditto.

> cheers,
>  Roland
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>

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