axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kellogg, Richard" <RKell...@MICROS.COM>
Subject RE: ws-axis/java/docs
Date Tue, 26 Oct 2004 11:57:08 GMT
Thank you. :)

Rick Kellogg

-----Original Message-----
From: Toshiyuki Kimura []
Sent: Tuesday, October 26, 2004 4:27 AM
Subject: Re: ws-axis/java/docs

Hi all of Axis committers and axis-dev folks,

   Now, we have a manual how to build our site with Apache Forrest.
This time, I made a new 'build.xml' to update, check and generate
the whole Axis site briefly. You can find out the manual on the
menu bar of our site as 'HowToBuildSite'.

   I believe that the task will help us to maintain the site easy,
and hopefully, we reduce the out of sync or wrong updates on the
site contents.


Toshi <>

On Sat, 23 Oct 2004, Toshiyuki Kimura wrote:

> Hi dims,
>  It's my pleasure.
>  I'd like to maintain the instructions for updating our site
> later. I'm also looking for an easy way to build the contents.
>  BTW, how long do we expose 'ws-axis/java/docs' to committers
> with a bit of risk for wrong updates in the near future ? As I
> mentioned before, it's enough to step down as read-only data.
> Yes, I can agree the priority is not so high. Just one thing,
> I hope I never do hand-to-hand synchronizing the sources. :-)
> Thanks,
> Toshi
> On Fri, 22 Oct 2004, Davanum Srinivas wrote:
>> Thanks a ton Toshi
>> On Fri, 22 Oct 2004 04:21:43 -0700 (PDT), Toshiyuki Kimura
>> <> wrote:
>>>    The site should be in sync with the latest sources now (hopefully).
>>> I picked up a lot of lost updates from 'ws-axis/java/docs', then I
>>> made modifications to the right contents - 'ws-axis/site' manually.
>>> That's very heavy work. :)
>>> Please don't update 'ws-axis/java/docs' any more from now on.
>>> Toshi <>
>>> On Wed, 20 Oct 2004, Toshiyuki Kimura wrote:
>>>> On Wed, 20 Oct 2004, Steve Loughran wrote:
>>>>> OK. I understand that this will update the site docs. How does this
>>>>> feed into the docs that come with the distribution of docs that end
>>>>> users see? Are we generating the in-distro docs ws-axis/java/docs
>>>>> from the forrest source in ws-axis/iste ? If so, yes, I have gone
>>>>> wrong. If not, well, we have a different problem.
>>>>  As you may know, our working space - has a lot
>>>> of roles as follows;
>>>>    a) Main web server for all project websites
>>>>    b) CVS root for Apache projects
>>>>    c) Subversion WebDAV access for Apache projects
>>>>    d) Rsync for mirroring
>>>>    e) Anonymous CVS for public CVS access
>>>>  I think it's especially important that the role a) as a public
>>>> Web server and b) as a CVS repository.  You can find the both of
>>>> master data for these two services on the server with ssh loggin.
>>>>  (Web server) ------- [/www/]
>>>>  (CVS repository) --- [/home/cvs/ws-axis]
>>>>                       [/home/cvs/ws-site]
>>>>  I think there're three key points on this issue.
>>>> [Point 1]
>>>>  The original sources, which are used to generate the static
>>>> contents by Forrest on the local computer of a committer, are
>>>> stored in minotaur as ws-axis/site, not as ws-axis/java/docs/.
>>>> I mean 'ws-axis/java/docs/' is no longer working as the master.
>>>>  Please let me check the update history for the targeted file...
>>>> <>
>>>>  Uhm, we moved to the current site about 1 year before. But the
>>>> 'invalid' content has been had a few updates excepting the last
>>>> one from you. I think that 'ws-axis/java/docs/' module should be
>>>> 'read only'. Is it possible and can we agree ?
>>>> [Point 2]
>>>>  The generated static contents have to be committed to 'ws-site'
>>>> module. For instance, if you're an axis committer, the destination
>>>> should be 'ws-site/target/axis/'. Moreover, please don't forget to
>>>> commit 'ws-axis/site' as the master source of the site.
>>>> [Point 3]
>>>>  The contents in 'ws-site/target/axis/' will be in sync with the
>>>> site data (i.e. /www/ automatically, there're a few
>>>> delays due to the cron shedule though.
>>>>  In any case, we have to import some of changes for the 'invalid'
>>>> contents(ws-axis/java/docs/) into the right contents(ws-axis/site).
>>>> The target might be under age 1 (year) at;
>>>> <>
>>>> Thanks,
>>>> Toshi
>> -- 
>> Davanum Srinivas -

View raw message