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>
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <4414873F.4030301@btopenworld.com>
Date: Sun, 12 Mar 2006 20:40:31 +0000
From: Stephen Colebourne <scolebourne@btopenworld.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [PROPOSAL][all] Break dependency on commons-build
References: <44130D48.40604@btopenworld.com>
	 <6bde122b0603120838u7ab6c8dam9ec25fe9e3812624@mail.gmail.com>
	 <4414503F.4020208@btopenworld.com> <1142194180.5453.10.camel@knossos.elmet>
In-Reply-To: <1142194180.5453.10.camel@knossos.elmet>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

robert burrell donkin wrote:
> why not give it a try and see if it improves things?

Both [lang] and [io] main sites are now updated via this new mechanism. 
Thus both [io] and [lang] now have no direct dependency on commons-build 
when building, whether from an svn checkout or from a released dist.

The full information is here:
http://wiki.apache.org/jakarta-commons/MavenWebsiteStucture

A key aspect of what I tried to do was KISS. It basically uses the 
internet and web standards (like @import in CSS) to make the direct 
connections rather than relative paths. The same is true of the entities 
- http entities are better supported than relative ones.

The single central CSS should also prove very useful at ApacheCon time.

I hope that a mavenite may be able to tell us if this helps us use maven 
1.1 as I understood that the relative paths were a headache.

Stephen

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