You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@forrest.apache.org by Ross Gardler <rg...@apache.org> on 2005/11/16 09:50:27 UTC

Publishing Our Site

crossley@apache.org wrote:
> Author: crossley
> Date: Tue Nov 15 15:26:03 2005
> New Revision: 344476
> 
> URL: http://svn.apache.org/viewcvs?rev=344476&view=rev
> Log:
> Automatic publish from forrestbot

Thanks David.

I think we should all do this more often. David is the only one who ever 
publishes the site. The process is real easy, there is no excuse for the 
rest of us to not help out.

So, when we make an important change to the site, lets also update the 
published version, there is a doc on how to do it in the etc folder.

Ross

Re: Publishing Our Site

Posted by Ross Gardler <rg...@apache.org>.

Cyriaque Dupoirieux wrote:
> Ross Gardler a écrit :
> 
>> crossley@apache.org wrote:
>>
>>> Author: crossley
>>> Date: Tue Nov 15 15:26:03 2005
>>> New Revision: 344476
>>>
>>> URL: http://svn.apache.org/viewcvs?rev=344476&view=rev
>>> Log:
>>> Automatic publish from forrestbot
>>
>>
>>
>> Thanks David.
>>
>> I think we should all do this more often. David is the only one who 
>> ever publishes the site. The process is real easy, there is no excuse 
>> for the rest of us to not help out.
>>
>> So, when we make an important change to the site, lets also update the 
>> published version, there is a doc on how to do it in the etc folder.
> 
> 
> 
> What is the difference with updating the doc and committing ?

The site that is available on the live server is pulled from a staging 
SVN server periodically. When we update our XDocs in svn this has no 
effect on the staging SVN.

We need to follow the process described in the file in etc to generate 
the site and update it on the staging server.

...

> Maybe we should have :
> 
>    * a deploy-batch target which uses the default message
>    * a deploy target which asks you to enter a commit message if
>      deploy.svn.commit-message has no value.

I've not looked at the scripts so can't help out there I'm afraid.

Ross

Re: Publishing Our Site

Posted by Cyriaque Dupoirieux <Cy...@pcotech.fr>.

Ross Gardler a écrit :

> crossley@apache.org wrote:
>
>> Author: crossley
>> Date: Tue Nov 15 15:26:03 2005
>> New Revision: 344476
>>
>> URL: http://svn.apache.org/viewcvs?rev=344476&view=rev
>> Log:
>> Automatic publish from forrestbot
>
>
> Thanks David.
>
> I think we should all do this more often. David is the only one who 
> ever publishes the site. The process is real easy, there is no excuse 
> for the rest of us to not help out.
>
> So, when we make an important change to the site, lets also update the 
> published version, there is a doc on how to do it in the etc folder.


What is the difference with updating the doc and committing ?

BTW in the publishing_our_site.txt (in /etc directory) there is a 
warning with the call

    * forrest -f publish.xml deploy -Ddeploy.svn.commit-message="my
      commit message"

Explaining that the commit message is not taken into account.
I have seen the forrestant.sh and it is not included as a java argument 
but as an ant parameter.
Maybe we should have :

    * a deploy-batch target which uses the default message
    * a deploy target which asks you to enter a commit message if
      deploy.svn.commit-message has no value.


Cyriaque,

>
> Ross
>
>