You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by bu...@apache.org on 2010/12/08 12:42:38 UTC
svn commit: r780269 -
/websites/staging/river/trunk/content/river/docs/index.html
Author: buildbot
Date: Wed Dec 8 11:42:38 2010
New Revision: 780269
Log:
Staging update by buildbot
Modified:
websites/staging/river/trunk/content/river/docs/index.html
Modified: websites/staging/river/trunk/content/river/docs/index.html
==============================================================================
--- websites/staging/river/trunk/content/river/docs/index.html (original)
+++ websites/staging/river/trunk/content/river/docs/index.html Wed Dec 8 11:42:38 2010
@@ -55,81 +55,19 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
-<!--
- ! Licensed to the Apache Software Foundation (ASF) under one
- ! or more contributor license agreements. See the NOTICE file
- ! distributed with this work for additional information
- ! regarding copyright ownership. The ASF licenses this file
- ! to you under the Apache License, Version 2.0 (the
- ! "License"); you may not use this file except in compliance
- ! with the License. You may obtain a copy of the License at
- !
- ! http://www.apache.org/licenses/LICENSE-2.0
- !
- ! Unless required by applicable law or agreed to in writing, software
- ! distributed under the License is distributed on an "AS IS" BASIS,
- ! WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- ! See the License for the specific language governing permissions and
- ! limitations under the License.
- !-->
-<body text="#000000" bgcolor="#ffffff" link="#9b37cc"
- vlink="#cc1877" alink="#ffffff">
-
-<p><title>Apache River Release Kit Index</title></p>
-<p><center><h1>Apache River Release<BR>v2.1.2</h1></center>
-<hr>
-<p>
-The Apache River release is based on the following two major contributions:
+<h1 id="jini_specification_and_documentation">Jini Specification and Documentation</h1>
+<p>The Apache River release is based on the following two major contributions:
the Jini Technology Starter Kit, and Service UI. In the documentation for this
release, you may see historical references to those releases.</p>
-<p>
-<UL>
-<LI><B><a href="info-index.html">Getting Started & More</a></B>
-<p>
-<LI><B>Informative reading</B>
- <ul>
- <li><i><a href="arch2_0.html">Jini<font size="-1"><sup>TM</sup></font> Architecture Specification Version 2.0 Extensions</a></i>
- <li><i><a href="specs/html/jini-spec.html">Jini<font size="-1"><sup>TM</sup>
-
-</font> Architecture Specification Version 1.0</a></i>
-
-</ul>
-<p>
-<LI><B><a href="release-notes/index.html">Release Notes</a></B>
-<p>
-<LI><B><a href="manpages-index.html">Manual Pages</a></B> for services, utilities, and tools
-<p>
-<LI><B><a href="spec-index.html">Specifications</a></B>
-<p>
-<LI><B>API documentation</B>
- <UL>
- <LI><a href="api/index.html"> Frames version</a>
- <LI><a href="api/overview-summary.html"> No Frames version</a>
- </UL>
-
-<p>
-
-</UL>
-<p>
-<p>
-<hr>
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-<ul>
- <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>
-</ul>
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-
-</body>
+<ul>
+<li><a href="info-index.html">Getting Started & More</a></li>
+<li>Informative reading</li>
+<li><a href="arch2_0.html">Jini<font size="-1"><sup>TM</sup></font> Architecture Specification Version 2.0 Extensions</a></li>
+<li><a href="specs/html/jini-spec.html">Jini<font size="-1"><sup>TM</sup></font> Architecture Specification Version 1.0</a></li>
+<li><a href="release-notes/index.html">Release Notes</a></li>
+<li><a href="manpages-index.html">Manual Pages</a> for services, utilities, and tools</li>
+<li><a href="spec-index.html">Specifications</a></li>
+</ul>
</div>
</td>
<td valign="top">
Re: svn commit: r780269 - /websites/staging/river/trunk/content/river/docs/index.html
Posted by Tom Hobbs <tv...@googlemail.com>.
Update: I've done the parent docs directory. I'm starting in the
specs directory now, if someone wants to take the release-notes one.
On Wed, Dec 8, 2010 at 2:47 PM, Tom Hobbs <tv...@googlemail.com> wrote:
> It is big. Also very boring.
>
> A link check when I'm done would be great, as I know already that some
> of the links are broken.
>
> I'm dropping some content as I go along because we have better docs
> elsewhere (e.g. the build instructions) but other things, like the
> activation.html and I'm sure others, I will make sure get linked to
> from somewhere.
>
> If anyone one wants to help I've started in the parent docs directory.
> There are the release-notes and specs directories that also need
> doing...
>
> On Wed, Dec 8, 2010 at 1:38 PM, Sim IJskes - QCG <si...@qcg.nl> wrote:
>> On 08-12-10 13:26, Tom Hobbs wrote:
>>>
>>> This is not fun work and i've not sorted the formatting out yet. Also
>>> I image that many of the links are broken.
>>>
>>> We certainly need to fix the "original Jini wiki" links, and probably
>>> put a link to the specs on the front page. I think it's more
>>> intuitive to have them there than on the "Documentation" sub-page, I
>>> can't explain my reasoning other than gut feel.
>>>
>>> I'd like to leave the link broken for now until I've got the specs in
>>> better order. I think that it's going to take a while...
>>
>> It curtainly looks like an huge job. We have to do the release notes for
>> every release. How do we do this in the future? We should give the release
>> notes their own directory, so we can keep a online archive of them for later
>> use. We could also give them their own style and sidebar.
>>
>> Do you want a linklint (link check) once in a while?
>>
>> Gr. Sim
>>
>> --
>> QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
>> Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
>>
>
Re: svn commit: r780269 - /websites/staging/river/trunk/content/river/docs/index.html
Posted by Tom Hobbs <tv...@googlemail.com>.
It is big. Also very boring.
A link check when I'm done would be great, as I know already that some
of the links are broken.
I'm dropping some content as I go along because we have better docs
elsewhere (e.g. the build instructions) but other things, like the
activation.html and I'm sure others, I will make sure get linked to
from somewhere.
If anyone one wants to help I've started in the parent docs directory.
There are the release-notes and specs directories that also need
doing...
On Wed, Dec 8, 2010 at 1:38 PM, Sim IJskes - QCG <si...@qcg.nl> wrote:
> On 08-12-10 13:26, Tom Hobbs wrote:
>>
>> This is not fun work and i've not sorted the formatting out yet. Also
>> I image that many of the links are broken.
>>
>> We certainly need to fix the "original Jini wiki" links, and probably
>> put a link to the specs on the front page. I think it's more
>> intuitive to have them there than on the "Documentation" sub-page, I
>> can't explain my reasoning other than gut feel.
>>
>> I'd like to leave the link broken for now until I've got the specs in
>> better order. I think that it's going to take a while...
>
> It curtainly looks like an huge job. We have to do the release notes for
> every release. How do we do this in the future? We should give the release
> notes their own directory, so we can keep a online archive of them for later
> use. We could also give them their own style and sidebar.
>
> Do you want a linklint (link check) once in a while?
>
> Gr. Sim
>
> --
> QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
> Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
>
Re: svn commit: r780269 - /websites/staging/river/trunk/content/river/docs/index.html
Posted by Sim IJskes - QCG <si...@qcg.nl>.
On 08-12-10 14:38, Sim IJskes - QCG wrote:
> It curtainly looks like an huge job. We have to do the release notes for
> every release. How do we do this in the future? We should give the
> release notes their own directory, so we can keep a online archive of
> them for later use. We could also give them their own style and sidebar.
For instance:
http://river.staging.apache.org/river/docs/release-notes/activation.html
Looks like much too valuable to 'just' be kept as release notes.
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: svn commit: r780269 - /websites/staging/river/trunk/content/river/docs/index.html
Posted by Sim IJskes - QCG <si...@qcg.nl>.
On 08-12-10 13:26, Tom Hobbs wrote:
> This is not fun work and i've not sorted the formatting out yet. Also
> I image that many of the links are broken.
>
> We certainly need to fix the "original Jini wiki" links, and probably
> put a link to the specs on the front page. I think it's more
> intuitive to have them there than on the "Documentation" sub-page, I
> can't explain my reasoning other than gut feel.
>
> I'd like to leave the link broken for now until I've got the specs in
> better order. I think that it's going to take a while...
It curtainly looks like an huge job. We have to do the release notes for
every release. How do we do this in the future? We should give the
release notes their own directory, so we can keep a online archive of
them for later use. We could also give them their own style and sidebar.
Do you want a linklint (link check) once in a while?
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: svn commit: r780269 - /websites/staging/river/trunk/content/river/docs/index.html
Posted by Tom Hobbs <tv...@googlemail.com>.
This is not fun work and i've not sorted the formatting out yet. Also
I image that many of the links are broken.
We certainly need to fix the "original Jini wiki" links, and probably
put a link to the specs on the front page. I think it's more
intuitive to have them there than on the "Documentation" sub-page, I
can't explain my reasoning other than gut feel.
I'd like to leave the link broken for now until I've got the specs in
better order. I think that it's going to take a while...
On Wed, Dec 8, 2010 at 12:02 PM, Peter Firmstone <ji...@zeus.net.au> wrote:
> Sweet work standardising the release notes formatting.
>
> I noticed our release notes are called original jini wiki on our main web
> page, hmm going to have to get around to fixing that ;)
>
> Cheers,
>
> Peter.
>
> buildbot@apache.org wrote:
>>
>> Author: buildbot
>> Date: Wed Dec 8 11:42:38 2010
>> New Revision: 780269
>>
>> Log:
>> Staging update by buildbot
>>
>> Modified:
>> websites/staging/river/trunk/content/river/docs/index.html
>>
>> Modified: websites/staging/river/trunk/content/river/docs/index.html
>>
>> ==============================================================================
>> --- websites/staging/river/trunk/content/river/docs/index.html (original)
>> +++ websites/staging/river/trunk/content/river/docs/index.html Wed Dec 8
>> 11:42:38 2010
>> @@ -55,81 +55,19 @@
>> <tr>
>> <td style="overflow: hidden;" valign="top" width="100%">
>> <div class="wiki-content">
>> -<!--
>> - ! Licensed to the Apache Software Foundation (ASF) under one
>> - ! or more contributor license agreements. See the NOTICE file
>> - ! distributed with this work for additional information
>> - ! regarding copyright ownership. The ASF licenses this file
>> - ! to you under the Apache License, Version 2.0 (the
>> - ! "License"); you may not use this file except in compliance
>> - ! with the License. You may obtain a copy of the License at
>> - ! - ! http://www.apache.org/licenses/LICENSE-2.0
>> - ! - ! Unless required by applicable law or agreed to in writing,
>> software
>> - ! distributed under the License is distributed on an "AS IS" BASIS,
>> - ! WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.
>> - ! See the License for the specific language governing permissions and
>> - ! limitations under the License.
>> - !-->
>> -<body text="#000000" bgcolor="#ffffff" link="#9b37cc"
>> - vlink="#cc1877" alink="#ffffff">
>> -
>> -<p><title>Apache River Release Kit Index</title></p>
>> -<p><center><h1>Apache River Release<BR>v2.1.2</h1></center>
>> -<hr>
>> -<p>
>> -The Apache River release is based on the following two major
>> contributions:
>> +<h1 id="jini_specification_and_documentation">Jini Specification and
>> Documentation</h1>
>> +<p>The Apache River release is based on the following two major
>> contributions:
>> the Jini Technology Starter Kit, and Service UI. In the documentation
>> for this
>> release, you may see historical references to those releases.</p>
>> -<p>
>> -<UL>
>> -<LI><B><a href="info-index.html">Getting Started & More</a></B>
>> -<p>
>> -<LI><B>Informative reading</B>
>> - <ul>
>> - <li><i><a href="arch2_0.html">Jini<font
>> size="-1"><sup>TM</sup></font> Architecture Specification Version 2.0
>> Extensions</a></i>
>> - <li><i><a href="specs/html/jini-spec.html">Jini<font
>> size="-1"><sup>TM</sup>
>> -
>> -</font> Architecture Specification Version 1.0</a></i>
>> -
>> -</ul> -<p>
>> -<LI><B><a href="release-notes/index.html">Release Notes</a></B>
>> -<p>
>> -<LI><B><a href="manpages-index.html">Manual Pages</a></B> for services,
>> utilities, and tools
>> -<p>
>> -<LI><B><a href="spec-index.html">Specifications</a></B>
>> -<p>
>> -<LI><B>API documentation</B>
>> - <UL>
>> - <LI><a href="api/index.html"> Frames version</a>
>> - <LI><a href="api/overview-summary.html"> No Frames version</a>
>> - </UL>
>> -
>> -<p>
>> -
>> -</UL>
>> -<p>
>> -<p>
>> -<hr>
>> -Licensed to the Apache Software Foundation (ASF) under one
>> -or more contributor license agreements. See the NOTICE file
>> -distributed with this work for additional information
>> -regarding copyright ownership. The ASF licenses this file
>> -to you under the Apache License, Version 2.0 (the
>> -"License"); you may not use this file except in compliance
>> -with the License. You may obtain a copy of the License at
>> -<ul>
>> - <a
>> href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>
>> -</ul>
>> -Unless required by applicable law or agreed to in writing, software
>> -distributed under the License is distributed on an "AS IS" BASIS,
>> -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>> -See the License for the specific language governing permissions and
>> -limitations under the License.
>> -
>> -</body>
>> +<ul>
>> +<li><a href="info-index.html">Getting Started & More</a></li>
>> +<li>Informative reading</li>
>> +<li><a href="arch2_0.html">Jini<font
>> size="-1"><sup>TM</sup></font> Architecture Specification Version 2.0
>> Extensions</a></li>
>> +<li><a href="specs/html/jini-spec.html">Jini<font
>> size="-1"><sup>TM</sup></font> Architecture Specification Version
>> 1.0</a></li>
>> +<li><a href="release-notes/index.html">Release Notes</a></li>
>> +<li><a href="manpages-index.html">Manual Pages</a> for services,
>> utilities, and tools</li>
>> +<li><a href="spec-index.html">Specifications</a></li>
>> +</ul>
>> </div>
>> </td>
>> <td valign="top">
>>
>>
>>
>>
>
>
Re: svn commit: r780269 - /websites/staging/river/trunk/content/river/docs/index.html
Posted by Peter Firmstone <ji...@zeus.net.au>.
Sweet work standardising the release notes formatting.
I noticed our release notes are called original jini wiki on our main
web page, hmm going to have to get around to fixing that ;)
Cheers,
Peter.
buildbot@apache.org wrote:
> Author: buildbot
> Date: Wed Dec 8 11:42:38 2010
> New Revision: 780269
>
> Log:
> Staging update by buildbot
>
> Modified:
> websites/staging/river/trunk/content/river/docs/index.html
>
> Modified: websites/staging/river/trunk/content/river/docs/index.html
> ==============================================================================
> --- websites/staging/river/trunk/content/river/docs/index.html (original)
> +++ websites/staging/river/trunk/content/river/docs/index.html Wed Dec 8 11:42:38 2010
> @@ -55,81 +55,19 @@
> <tr>
> <td style="overflow: hidden;" valign="top" width="100%">
> <div class="wiki-content">
> -<!--
> - ! Licensed to the Apache Software Foundation (ASF) under one
> - ! or more contributor license agreements. See the NOTICE file
> - ! distributed with this work for additional information
> - ! regarding copyright ownership. The ASF licenses this file
> - ! to you under the Apache License, Version 2.0 (the
> - ! "License"); you may not use this file except in compliance
> - ! with the License. You may obtain a copy of the License at
> - !
> - ! http://www.apache.org/licenses/LICENSE-2.0
> - !
> - ! Unless required by applicable law or agreed to in writing, software
> - ! distributed under the License is distributed on an "AS IS" BASIS,
> - ! WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> - ! See the License for the specific language governing permissions and
> - ! limitations under the License.
> - !-->
> -<body text="#000000" bgcolor="#ffffff" link="#9b37cc"
> - vlink="#cc1877" alink="#ffffff">
> -
> -<p><title>Apache River Release Kit Index</title></p>
> -<p><center><h1>Apache River Release<BR>v2.1.2</h1></center>
> -<hr>
> -<p>
> -The Apache River release is based on the following two major contributions:
> +<h1 id="jini_specification_and_documentation">Jini Specification and Documentation</h1>
> +<p>The Apache River release is based on the following two major contributions:
> the Jini Technology Starter Kit, and Service UI. In the documentation for this
> release, you may see historical references to those releases.</p>
> -<p>
> -<UL>
> -<LI><B><a href="info-index.html">Getting Started & More</a></B>
> -<p>
> -<LI><B>Informative reading</B>
> - <ul>
> - <li><i><a href="arch2_0.html">Jini<font size="-1"><sup>TM</sup></font> Architecture Specification Version 2.0 Extensions</a></i>
> - <li><i><a href="specs/html/jini-spec.html">Jini<font size="-1"><sup>TM</sup>
> -
> -</font> Architecture Specification Version 1.0</a></i>
> -
> -</ul>
> -<p>
> -<LI><B><a href="release-notes/index.html">Release Notes</a></B>
> -<p>
> -<LI><B><a href="manpages-index.html">Manual Pages</a></B> for services, utilities, and tools
> -<p>
> -<LI><B><a href="spec-index.html">Specifications</a></B>
> -<p>
> -<LI><B>API documentation</B>
> - <UL>
> - <LI><a href="api/index.html"> Frames version</a>
> - <LI><a href="api/overview-summary.html"> No Frames version</a>
> - </UL>
> -
> -<p>
> -
> -</UL>
> -<p>
> -<p>
> -<hr>
> -Licensed to the Apache Software Foundation (ASF) under one
> -or more contributor license agreements. See the NOTICE file
> -distributed with this work for additional information
> -regarding copyright ownership. The ASF licenses this file
> -to you under the Apache License, Version 2.0 (the
> -"License"); you may not use this file except in compliance
> -with the License. You may obtain a copy of the License at
> -<ul>
> - <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>
> -</ul>
> -Unless required by applicable law or agreed to in writing, software
> -distributed under the License is distributed on an "AS IS" BASIS,
> -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> -See the License for the specific language governing permissions and
> -limitations under the License.
> -
> -</body>
> +<ul>
> +<li><a href="info-index.html">Getting Started & More</a></li>
> +<li>Informative reading</li>
> +<li><a href="arch2_0.html">Jini<font size="-1"><sup>TM</sup></font> Architecture Specification Version 2.0 Extensions</a></li>
> +<li><a href="specs/html/jini-spec.html">Jini<font size="-1"><sup>TM</sup></font> Architecture Specification Version 1.0</a></li>
> +<li><a href="release-notes/index.html">Release Notes</a></li>
> +<li><a href="manpages-index.html">Manual Pages</a> for services, utilities, and tools</li>
> +<li><a href="spec-index.html">Specifications</a></li>
> +</ul>
> </div>
> </td>
> <td valign="top">
>
>
>
>