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: error (idunn.apache.osuosl.org: domain apache.org from
 82.209.166.4 cause and error)
Message-ID: <4512F1D1.7080004@apache.org>
Date: Thu, 21 Sep 2006 22:10:57 +0200
From: Dennis Lundberg <dennisl@apache.org>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: How to make site updates?
References: <45117A22.4090503@noaa.gov> <4511A38B.4040601@apache.org>
 <4512AFA6.2070102@noaa.gov>
In-Reply-To: <4512AFA6.2070102@noaa.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

You can find out a lot about the Maven site plugin, which is used to 
generate and deploy the site, on this page:
   http://maven.apache.org/plugins/maven-site-plugin/howto.html

Better documentation has been developed, but has not been officially 
published yet.

-- 
Dennis Lundberg

Kris Nuttycombe wrote:
> The site looks pretty good, although it appears that there may be some 
> CSS problems - the left navigation bar is floated over the body content 
> in both Firefox and Konqueror; I'm not sure how it shows up in IE.
> 
> So, how do I go about deploying the site?
> 
> Kris
> 
> Dennis Lundberg wrote:
>> Kris Nuttycombe wrote:
>>> Hi, all,
>>>
>>> What is the general process for making updates to a project site? 
>>> There have been a number of changes to the pipeline documentation and 
>>> the javadocs need to be regenerated. How do I go about making these 
>>> changes visible? The project is using maven2 and the default 
>>> templates for site generation, so how do I go about getting the 
>>> standard commons look & feel?
>>>
>>> Thanks,
>>>
>>> Kris
>>
>> Hi Kris
>>
>> You should get the standard look & feel automatically by pom 
>> inheritance. It doesn't look exactly like the Maven 1 generated sites 
>> yet, but we're slowly getting there. Please post any differences you 
>> spot here, and I'll try to fix them. The long-term solution for this 
>> is to create a commons-skin for Maven 2.
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 


-- 
Dennis Lundberg

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