Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Content-Class: urn:content-classes:message
Message-ID: <3FBFCB5A.8020208@steitz.com>
Date: Sat, 22 Nov 2003 13:47:22 -0700
From: "Phil Steitz" <phil@steitz.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830
MIME-Version: 1.0
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [site] Non-Maven web sites
References: <20031122114613.H76618@minotaur.apache.org>
Content-Type: text/plain;
	format=flowed;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Martin Cooper wrote:
> I've updated the wiki page with the current status of all Commons Proper
> sites (and some of the sandbox sites). See:
> 
> http://nagoya.apache.org/wiki/apachewiki.cgi?CreatingStandardWebPresence
> 
> The main thing that struck me, when putting this together, is the number
> of components that have both Maven and non-Maven sites. In all such cases,
> the non-Maven site is the one linked to from the main Commons page. The
> components in this state are:
> 
>   BeanUtils
>   Collections
>   Digester
>   Discovery
>   Jexl
>   Lang
>   Logging
>   Modeler
> 
> Is there any reason why we should not switch over to the Maven sites as
> the main sites right now, and "deprecate" the non-Maven versions?

There are two things that need to be resolved to make this happen, 
AFAIK.  First, we need to settle the issue of what goes in CVS.  If "all 
generated HTML" is the answer, we need to get all of the maven-generated 
HTML committed (many megs of redundant content, many redundant commit 
messages IMHO).  Second, we need to agree on a common nav (as stated on 
the Wiki page).  My vote would be to use commons/incl_nav uniformly. 
Several of the existing maven sites (both linked and unlinked) don't 
include this.  I also agree with the Wiki proposal for the "standard" 
pages (FAQ, examples, etc).

I deployed the lang maven site a couple of weeks ago and have been 
waiting to see where the CVS debate ended up (and some cleanup of the 
main site, so I could safely regenerate and commit all of the nav 
changes) before linking it (with some fixes).

I am willing to help with this, starting with [lang] and [collections], 
first getting the basic sites out and then adding the missing pages. I 
am also willing to help document whatever site generation / cvs update 
process we agree on.

Can we agree to omit the maven-generated HTML from cvs and use 
commons/incl_nav for the standard nav?

Phil

> 
> Other notable issues with Commons Proper components:
> 
>  * EL does not currently have a Maven site.
>  * Launcher has no web presence at all, despite being a Proper component.
> 
> The Sandbox is not a pretty sight at all, but IMHO we should get Proper to
> where we want it to be first, and then bring Sandbox up to the same level.
> 
> --
> Martin Cooper
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 


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