portals-pluto-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nloth...@apache.org
Subject svn commit: r109280 - /portals/pluto/trunk/xdocs/changes.xml /portals/pluto/trunk/xdocs/developer/subversion.xml /portals/pluto/trunk/xdocs/install.xml
Date Wed, 01 Dec 2004 04:30:01 GMT
Author: nlothian
Date: Tue Nov 30 20:30:00 2004
New Revision: 109280

URL: http://svn.apache.org/viewcvs?view=rev&rev=109280
Log:
Updated documentation
Modified:
   portals/pluto/trunk/xdocs/changes.xml
   portals/pluto/trunk/xdocs/developer/subversion.xml
   portals/pluto/trunk/xdocs/install.xml

Modified: portals/pluto/trunk/xdocs/changes.xml
Url: http://svn.apache.org/viewcvs/portals/pluto/trunk/xdocs/changes.xml?view=diff&rev=109280&p1=portals/pluto/trunk/xdocs/changes.xml&r1=109279&p2=portals/pluto/trunk/xdocs/changes.xml&r2=109280
==============================================================================
--- portals/pluto/trunk/xdocs/changes.xml	(original)
+++ portals/pluto/trunk/xdocs/changes.xml	Tue Nov 30 20:30:00 2004
@@ -5,6 +5,37 @@
 <body>
 
 <release version="1.0.1-rc2" date="n/a" description="Release Candidate">
+  <action dev="nlothian" type="update">
+	Update FAQ and installation instructions.
+  </action>
+  <action dev="nlothian" type="update">
+	Update version number to 1.0.1-rc2 in \project.xml, \deploy\project.xml, \portal\project.xml,
\testsuite\project.xml, 
+	\container\src\conf\org\apache\pluto\environment.properties and \portal\src\webapp\WEB-INF\config\services\ConfigService.properties
+  </action>
+  <action dev="nlothian" type="fix">
+    Altered PortalActionProvider to suit Jetspeed better. See http://nagoya.apache.org/jira/browse/PLUTO-64
+  </action>
+  <action dev="nlothian" type="fix">
+    Modified RenderResponseImpl.isValidContentType to correctly handle wildcard mime types.
See http://nagoya.apache.org/jira/browse/PLUTO-84
+  </action>
+  <action dev="nlothian" type="fix">
+    Fixed to allow Pluto to work when disconnected from Internet. See http://nagoya.apache.org/jira/browse/PLUTO-88
+  </action>
+  <action dev="nlothian" type="fix">
+    Fixed spelling error on login_success.jsp
+  </action>
+  <action dev="nlothian" type="fix">
+    Fixed TestSuite web.xml to be valid. http://nagoya.apache.org/jira/browse/PLUTO-81
+  </action>
+  <action dev="nlothian" type="fix">
+    Fix for renderResponse.getNamespace() returns invalid Javascript name. See http://nagoya.apache.org/jira/browse/PLUTO-85
+  </action>
+  <action dev="nlothian" type="add">
+    Patch from Craig Doremus to allow portlet deployment using Ant. See http://nagoya.apache.org/jira/browse/PLUTO-72
+  </action>
+  <action dev="nlothian" type="update">
+    Updated build.properties.sample to use Tomcat 5 by default
+  </action>
   <action dev="ddewolf" type="add">
     Added FAQ documentation.
   </action>
@@ -22,7 +53,7 @@
   <action dev="ddewolf" type="fix">
     PortalURLs were incorrectly converting null values to the String
     "null".  This was happending when action requests with a query
-    string such as: <code>?param=&amp;param2=</code>.  
+    string such as: <code>?param=&amp;param2=</code>.
   </action>
   <action dev="ddewolf" type="fix">
     Issue PLUTO-66.  The testsuite TestPortlet was not testing
@@ -36,7 +67,7 @@
     Thank you Ken Ramirez.
   </action>
   <action dev="ddewolf" type="update">
-    Add README file to all releases.  Thank you Craig Doremus for pointing 
+    Add README file to all releases.  Thank you Craig Doremus for pointing
     out that it wasn't included.
   </action>
   <action dev="ddewolf" type="fix">
@@ -69,7 +100,7 @@
     (<A href="http://nagoya.apache.org/jira/browse/PLUTO-49">PLUTO-49</A>)
   </action>
   <action dev="ddewolf" type="fix">
-    Implement Mime Type Matching.  
+    Implement Mime Type Matching.
     (<A href="http://nagoya.apache.org/jira/browse/PLUTO-55">PLUTO-55</A>)
   </action>
   <action dev="cziegeler" type="fix">
@@ -83,7 +114,7 @@
 <release version="1.0" date="2003" description="Initial CVS Import">
    <action dev="cziegeler" type="update">
     Updating to the new ASF License 2.0.
-   </action>              
+   </action>
 </release>
 
   </body>

Modified: portals/pluto/trunk/xdocs/developer/subversion.xml
Url: http://svn.apache.org/viewcvs/portals/pluto/trunk/xdocs/developer/subversion.xml?view=diff&rev=109280&p1=portals/pluto/trunk/xdocs/developer/subversion.xml&r1=109279&p2=portals/pluto/trunk/xdocs/developer/subversion.xml&r2=109280
==============================================================================
--- portals/pluto/trunk/xdocs/developer/subversion.xml	(original)
+++ portals/pluto/trunk/xdocs/developer/subversion.xml	Tue Nov 30 20:30:00 2004
@@ -1,62 +1,103 @@
-<?xml version="1.0"?>
-<!-- 
-Copyright 2004 The Apache Software Foundation
-Licensed  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.
--->
-<document>
-<properties>
-  <author email="ddewolf@apache.org">David DeWolf</author>
-  <title>Developer Guide: Obtaining the Source Code</title>
-</properties>
-
-<body>
-  <section name="Developer Guide: Obtaining the Source Code">
-  <p>
-    There are several reasons why you may want to have access to
-    the pluto source code.  Some may want to participate in 
-    the development of Pluto by submiting patches.  Others may want
-    to utilize Pluto as a reference implementation to clarify
-    the Portlet Specification.  Whatever the reason, there are two
-    ways to access the source code.
-  </p>
-
-  <p>
-    <A href="#Downloading_the_Source_Distribution">Downloading the
-    most recent Source Distribution</A> is the easiest
-    way to access the source.  Of course, because this method is 
-    reliant on realeases, you may not have the most recent source.
-    That said, you do have a better chance at recieving a more
-    stable codebase if you are using a distiribution.
-  </p>
-
-  <p>
-    <A href="#Using_Subversion">Using Subversion</A> to checkout the
-    absolute up-to-date version of the code is the best way to
-    retrieve the source code.  If you plan to submit patches, 
-    we ask that you use the Subversion Trunk to create your
-    diffs.
-  </p>
-    
-    <subsection name="Downloading the Source Distribution">
-
-    </subsection>
-
-    <subsection name="Using Subversion">
-
-    </subsection>
-
-  </section>
-</body>
-</document>
+<?xml version="1.0"?>
+<!--
+Copyright 2004 The Apache Software Foundation
+Licensed  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.
+-->
+<document>
+<properties>
+  <author email="ddewolf@apache.org">David DeWolf</author>
+  <title>Developer Guide: Obtaining the Source Code</title>
+</properties>
+
+<body>
+  <section name="Developer Guide: Obtaining the Source Code">
+  <p>
+    There are several reasons why you may want to have access to
+    the pluto source code.  Some may want to participate in
+    the development of Pluto by submiting patches.  Others may want
+    to utilize Pluto as a reference implementation to clarify
+    the Portlet Specification.  Whatever the reason, there are two
+    ways to access the source code.
+  </p>
+
+  <p>
+    <A href="#Downloading_the_Source_Distribution">Downloading the
+    most recent Source Distribution</A> is the easiest
+    way to access the source.  Of course, because this method is
+    reliant on releases, you may not have the most recent source.
+    That said, you do have a better chance at recieving a more
+    stable codebase if you are using a distiribution.
+  </p>
+
+  <p>
+    <A href="#Using_Subversion">Using Subversion</A> to checkout the
+    absolute up-to-date version of the code is the best way to
+    retrieve the source code.  If you plan to submit patches,
+    we ask that you use the Subversion Trunk to create your
+    diffs.
+  </p>
+
+    <subsection name="Downloading the Source Distribution">
+		<p>See the <a href="mirrors.cgi">download instructions</a></p>
+    </subsection>
+
+    <subsection name="Using Subversion">
+		<p>The Pluro project uses the
+		<a href="http://subversion.tigris.org/">Subversion</a> version control
+		system.  If you're new to Subversion, you can check out the
+		<a href="http://svnbook.red-bean.com/">online book</a> about Subversion.
+		Note that we are currently using Subversion 1.1.x (there are separate
+		versions of the book covering 1.0 and 1.1).</p>
+
+    	<h2>Web Access to Subversion</h2>
+		<p>
+		If you just want to browse the source code, you can use the
+		<a
+		href="http://svn.apache.org/viewcvs.cgi/portals/pluto/trunk/?root=Apache-SVN    ">ViewCVS
+		web interface</a> to Subversion.  This is current at all times.
+		</p>
+
+		<h2>Normal Subversion Access</h2>
+		<p>Anyone can check code out of Subversion.  You only need to specify a
+		username and password in order to update the Subversion repository, and only
+		Pluto committers have the permissions to do that.  We run Subversion
+		over standard HTTPS, so hopefully you won't have problems with intervening
+		firewalls.</p>
+
+		<h3>Check out from Subversion</h3>
+		<p>Again, anyone can do this.  Use a command like:</p>
+		<pre>svn checkout https://svn.apache.org/repos/asf/portals/pluto/trunk/ pluto</pre>
+
+		<h3>Commit Changes to Subversion</h3>
+		<p>Any Pluto committer should have a shell account on
+		<tt>svn.apache.org</tt>.  Before you can commit, you'll need to set a
+		Subversion password for yourself.  To do that, log in to
+		<tt>svn.apache.org</tt> and run the command <strong>svnpasswd</strong>.</p>
+
+		<p>Once your password is set, you can use a command like this to commit:</p>
+		<pre>svn commit</pre>
+		<p>If Subversion can't figure out your username, you can tell it
+		explicitly:</p>
+		<pre>svn --username you commit</pre>
+		<p>Subversion will prompt you for a password, and once you enter it once, it
+		will remember it for you.  Note this is the password you configured with
+		<tt>svnpasswd</tt>, not your shell or other password.</p>
+
+		<p>Thanks to <a href="http://geronimo.apache.org/">The Geronimo group</a>
for these docs.</p>
+    </subsection>
+
+  </section>
+</body>
+</document>

Modified: portals/pluto/trunk/xdocs/install.xml
Url: http://svn.apache.org/viewcvs/portals/pluto/trunk/xdocs/install.xml?view=diff&rev=109280&p1=portals/pluto/trunk/xdocs/install.xml&r1=109279&p2=portals/pluto/trunk/xdocs/install.xml&r2=109280
==============================================================================
--- portals/pluto/trunk/xdocs/install.xml	(original)
+++ portals/pluto/trunk/xdocs/install.xml	Tue Nov 30 20:30:00 2004
@@ -1,9 +1,9 @@
 <?xml version="1.0"?>
-<!-- 
+<!--
 Copyright 2004 The Apache Software Foundation
 Licensed  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 
+You may obtain a copy of the License at
 
 http://www.apache.org/licenses/LICENSE-2.0
 
@@ -36,10 +36,10 @@
 
 <subsection name="Binary Distribution">
 <p>The binary distribution of Pluto is packaged with Tomcat
-   (currently version 5.0.28).  Pluto leverages Tomcat to 
-   provide the web container in which the Pluto portlet 
-   container executes. The binary distribution includes 
-   the Pluto Portlet Container, The Portal Driver, and 
+   (currently version 5.0.28).  Pluto leverages Tomcat to
+   provide the web container in which the Pluto portlet
+   container executes. The binary distribution includes
+   the Pluto Portlet Container, The Portal Driver, and
    Pluto Testsuite.</p>
 <p>To install the binary distribution:
    <ul>
@@ -47,10 +47,10 @@
        the current binary distribution of Pluto</li>
    <li>Extract the binary distribution to a directory
        from here forward refered to as "&lt;PLUTO_HOME&gt;".</li>
-   <li>Startup the server by using the appropriate tomcat 
+   <li>Startup the server by using the appropriate tomcat
        startup script located at &lt;PLUTO_HOME&gt;/bin.
        For *nix use startup.sh; for windows use startup.bat.</li>
-   <li>Point your browser to 
+   <li>Point your browser to
        <A href="http://localhost:8080/pluto/portal">The Pluto Driver</A>
        and your ready to go!</li>
    </ul>
@@ -70,7 +70,7 @@
 <subsection name="Source Distribution">
 <p>Installing the source distribution requires the most effort,
    and is recomended only for those individuals who are interested
-   in modifying the container.  The source distribution is 
+   in modifying the container.  The source distribution is
    basically a snapshot of the source code repository at a given
    time. Because of this, please see the build instructions, which
    will provide information about how to build Pluto from scratch.
@@ -79,7 +79,7 @@
    <ul>
    <li>Install Java 1.3 or greater</li>
    <li>Install Maven 1.0 or greater</li>
-   <li>Install Tomcat 4.x or Tomcat 5.x to 
+   <li>Install Tomcat 4.x or Tomcat 5.x to
        a directory from here forward refered to as
        &lt;TOMCAT_HOME&gt;</li>
    <li>Edit your &lt;PLUTO_HOME&gt;/build.properties to include
@@ -87,18 +87,18 @@
        <table><tr><th>Property</th><th>Value</th><th>Example(s)</th></tr>
               <tr><td>maven.tomcat.home</td>
                   <td>Tomcat Installation Directory</td>
-                  <td><code>\\usr\\local\\jakarta-tomcat.5.0.27</code>,

+                  <td><code>\\usr\\local\\jakarta-tomcat.5.0.27</code>,
                       <code>c:\\jakarta-tomcat.5.0.27</code></td></tr>
               <tr><td>maven.tomcat.version.major</td>
                   <td>Tomcat Major Version Number</td>
                   <td>5</td></tr>
        </table></li>
-    <li>From &lt;PLUTO_HOME&gt; issue the command: 
+    <li>From &lt;PLUTO_HOME&gt; issue the command:
         <code>'maven fullDeployment'</code></li>
-    <li>Startup the server by using the appropriate tomcat 
+    <li>Startup the server by using the appropriate tomcat
        startup script located at &lt;PLUTO_HOME&gt;/bin.
        For *nix use startup.sh; for windows use startup.bat.</li>
-    <li>Point your browser to 
+    <li>Point your browser to
        <A href="http://localhost:8080/pluto/portal">The Pluto Driver</A>
        and your ready to go!</li>
    </ul>
@@ -120,9 +120,11 @@
       <p>This can be done by:
          <pre>maven deploy -Ddeploy=/MyPathToMyPortlet/target/MyPortlet.war</pre>
       </p>
-      <p>TODO: There are properties, etc. . .that must be set
-         in order for this to work properly.  They should be
-         specified here.</p></li>
+      <p>See the <a href="developer\build_source.html">Building From Source</a>
document for detailed instructions.</p></li>
+
+	<p>Alternatively, there is an interactive ant script in the <tt>portlet-deploy</tt>
directory
+	that will perform the same task as the Maven deployment goal.</p>
+
   <li>Modify the Portlet Entity Registry and the Page Registry files.  These
       configuration files are located at:
 <pre>
@@ -132,11 +134,11 @@
 </pre>
 
 <p>
-The Portlet entity registry file requires that you specify an application and 
-a Portlet ID for your new Portlet. The Application ID must be unique. It also 
-needs to know the name of the Portlet so that it can go out and find it in 
-the webapps path. Furthermore, this information is used to map the Portlet 
-name to the appropriate class path for loading the class. The following is an 
+The Portlet entity registry file requires that you specify an application and
+a Portlet ID for your new Portlet. The Application ID must be unique. It also
+needs to know the name of the Portlet so that it can go out and find it in
+the webapps path. Furthermore, this information is used to map the Portlet
+name to the appropriate class path for loading the class. The following is an
 example of some additions you can make to the entity registry file:
 </p>
 
@@ -150,7 +152,7 @@
 </pre>
 
 <p>
-The page registry provides Pluto with the layout information for your Portlet. 
+The page registry provides Pluto with the layout information for your Portlet.
 The names used in the fragments must be unique as done in the following example:
 </p>
 

Mime
View raw message