portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tay...@apache.org
Subject cvs commit: jakarta-jetspeed-2/archives/ApachePortals/xdocs/status 2004-03.xml
Date Fri, 26 Mar 2004 00:18:16 GMT
taylor      2004/03/25 16:18:16

  Added:       archives/ApachePortals .cvsignore README.txt
                        project.properties project.xml
               archives/ApachePortals/xdocs download.xml
                        getting-started.xml index.xml issue-tracking.xml
                        javadocs.xml license.xml mission.xml navigation.xml
                        news.xml powered.xml supporting.xml wiki.xml
               archives/ApachePortals/xdocs/development code-standards.xml
                        developer-links.xml documentation.xml
                        further-reading.xml
               archives/ApachePortals/xdocs/images apache-portals-2.gif
                        apache-portals-big.gif apache-portals-bw.gif
                        apache-portals.gif apache.gif jetspeed-powered.gif
               archives/ApachePortals/xdocs/status 2004-03.xml
  Log:
  Apache Portals site
  Putting it here so others can work on it
  Hope to get a cvs created soon for portals-site
  
  Revision  Changes    Path
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/.cvsignore
  
  Index: .cvsignore
  ===================================================================
  docs
  build.properties
  velocity.log
  maven.log
  target
  .project
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/README.txt
  
  Index: README.txt
  ===================================================================
  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.
  
  $Id: README.txt,v 1.1 2004/03/26 00:18:16 taylor Exp $
  
  The Apache Portals Website Instructions
  ----------------------------------------
  
  The Apache Portals web site is based on .xml files which are transformed
  into .html files using Maven.
  
  http://maven.apache.org/
  
  Once you have the site checked out locally, cd into your
  portals-site directory and execute:
  
  maven site
  
  This will build the documentation into the target/docs/ directory. The output
  will show you which files got re-generated.
  
  If you would like to make modifications to the web site documents,
  you simply need to edit the files in the xdocs/ directory.
  
  Once you have built your documentation and confirmed that your changes are
  ok, you can check your .xml files back into CVS.
  
  To deploy the site execute:
  
  maven site:deploy
  
  To do this you need an account on the jakarta.apache.org machine!!
  
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/project.properties
  
  Index: project.properties
  ===================================================================
  maven.xdoc.date=left
  maven.xdoc.version=
  maven.xdoc.includeProjectDocumentation=no
  maven.xdoc.poweredby.image=
  maven.xdoc.poweredby.title=
  maven.xdoc.poweredby.url=
  maven.xdoc.date = left
  
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/project.xml
  
  Index: project.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  
  <project>
    <pomVersion>3</pomVersion>
    <name>Apache Portals</name>
    <id>portals-site</id>
    <currentVersion>1.0</currentVersion>
    <organization>
      <name>Apache Software Foundation</name>
      <url>http://www.apache.org/</url>
      <logo>/images/apache.gif</logo>
    </organization>
    <inceptionYear>2004</inceptionYear>
    <package>org.apache</package>
    <logo>/images/apache-portals.gif</logo>
    <shortDescription>Apache Portals houses open source portal technology projects.</shortDescription>
    <description>
      <b>Apache Portals</b> exists to promote the use of open source portal technology.
      We view portals as an important technology in in the growing portal and web application environments.  
      We intend to build freely available portal software in order to promote the use of this technology.
    </description>
    <url>http://portals.apache.org/</url>
    <issueTrackingUrl>http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10492</issueTrackingUrl>
    <siteAddress>portals.apache.org</siteAddress>
    <siteDirectory>/www/portals.apache.org/</siteDirectory>
  
    <repository>
      <connection>scm:cvs:pserver:anoncvs@cvs.apache.org:/home/cvspublic:portals-site</connection>
      <developerConnection>scm:cvs:ext:${maven.username}@cvs.apache.org:/home/cvs:portals-site</developerConnection>
      <url>http://cvs.apache.org/viewcvs/portals-site/</url>
    </repository>
  
    <mailingLists>
      <mailingList>
        <name>Portals User List</name>
        <subscribe>portals-general-subscribe@portals.apache.org</subscribe>
        <unsubscribe>portals-general-unsubscribe@portals.apache.org</unsubscribe>
        <archive>http://archives.apache.org/eyebrowse/SummarizeList?listName=portals-general@portals.apache.org</archive>
      </mailingList>
    </mailingLists>
    <developers>
      <developer>
        <name>David Sean Taylor</name>
        <id>taylor</id>
        <email>taylor at apache.org</email>
        <roles>
          <role>Java Developer</role>
        </roles>
      </developer>
  
      <developer>
        <name>Raphael Luta</name>
        <id>raphael</id>
        <email>raphael at apache.org</email>
        <roles>
          <role>Java Developer</role>
        </roles>
      </developer>
  
      <developer>
        <name>Santiago Gala</name>
        <id>santiago</id>
        <email>santiago at apache.org</email>
        <roles>
          <role>Java Developer</role>
        </roles>
      </developer>
  
  
      <developer>
        <name>Mark Orciuch</name>
        <id>mark</id>
        <email>mark_oriuch at nqsltd.com</email>
        <roles>
          <role>Java Developer</role>
        </roles>
      </developer>
  
      <developer>
        <name>Paul Spencer</name>
        <id>paulsp</id>
        <email>paulsp at apache.org</email>
        <roles>
          <role>Java Developer</role>
        </roles>
      </developer>
  
      <developer>
        <name>Scott Weaver</name>
        <id>weaver</id>
        <email>weaver at apache.org</email>
        <roles>
          <role>Java Developer</role>
        </roles>
      </developer>
  
      <developer>
        <name>Roger Ruttimann</name>
        <id>roger</id>
        <email>roger.ruttimann at earthlink.net</email>
        <roles>
          <role>Java Developer</role>
        </roles>
      </developer>
      <developer>
          <name>Michael Blum</name>
          <id>blumm</id>
          <email>blumm at apache.org</email>
          <roles>
             <role>Java Developer</role>
          </roles>
      </developer>
  
      <developer>
          <name>Stefan Hepper</name>
          <id>sthepper</id>
          <email>sthepper at apache.org</email>
          <roles>
             <role>Java Developer</role>
          </roles>
      </developer>
  
      <developer>
          <name>Carsten Ziegeler</name>
          <id>cziegeler</id>
          <email>cziegeler at apache.org</email>
          <roles>
             <role>Java Developer</role>
          </roles>
      </developer>
  
      <developer>
          <name>David DeWolf</name>
          <id>ddewolf</id>
          <email>ddewolf at apache.org</email>
          <roles>
             <role>Java Developer</role>
          </roles>
      </developer>
  
      <developer>
          <name>Nick Lothian</name>
          <id>nlothian</id>
          <email>nlothian at apache.org</email>
          <roles>
             <role>Java Developer</role>
          </roles>
      </developer>
  
      <developer>
        <name>David Le Strat</name>
        <id>dls</id>
        <email>dlestrat at apache.org</email>
        <roles>
          <role>Java Developer</role>
        </roles>
      </developer>
      
      <developer>
        <name>Jeremy Ford</name>
        <id>jford</id>
        <email>jford at apache.org</email>
        <roles>
          <role>Java Developer</role>
        </roles>
      </developer>
  
  
    </developers>
    <dependencies></dependencies>
    <build>
      <sourceDirectories></sourceDirectories>
      <aspectSourceDirectories></aspectSourceDirectories>
      <unitTestPatterns></unitTestPatterns>
      <jarResources></jarResources>
      <jars></jars>
    </build>
    
    <reports>
      <report>maven-developer-activity-plugin</report>
      <report>maven-file-activity-plugin</report>
    </reports>
  </project>
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/download.xml
  
  Index: download.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
  
    <properties>
      <author email="taylor@apache.org">David Sean Taylor</author>
      <title>Downloading Apache Portal Projects</title>
    </properties>
  
  <body>
  
  <section name="Downloading Releases">
  <p>
  Official releases of the Apache Portals projects can be downloaded from the Apache Mirror System.
  See the <b>Binary and Source Distribution</b> section below for downloading releases.
  </p>
  <subsection name="Releases: Binary And Source Distributions">
    <p>
     To download the latest releases as binaries or source, you can get them from the
      <a href="http://www.apache.org/dyn/closer.cgi">Apache Mirror System</a>
      in the /portals subdirectory.
    </p>
  </subsection>
  
  <subsection name="Nightly Build Snapshots">
    <p>
      Apache Portals currently does not provicde nightly snapshot builds.
    </p>
  </subsection>
  
  <subsection name="CVS">
    <p>
      You can check out the latest source from the Apache Portals CVS modules.
      Information on connecting to the Apache Portals repositories is found 
      <a href="cvs-usage.html">here</a>.
    </p>
  </subsection>
  
  <subsection name="Building The Source">
    <p>
      Be sure and read the GETTING-STARTED documentation for each Apache Portals project
      for instructions on how to build the project.
      Apache Portal projects require <a href="http://maven.apache.org">Maven</a> as its 
      build system, and building is usually as simple as running 'maven' or 'maven jar:jar'
      at the top of the source directory. Builds vary on a per project basis.
    </p>
  </subsection>
  </section>
  </body>
  </document>
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/getting-started.xml
  
  Index: getting-started.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
  
    <properties>
      <author email="taylor@apache.org">David Sean Taylor</author>
      <title>Getting Involved</title>
    </properties>
  
  <body>
  
  <section name="Getting Started">
  <p>
  Apache Portals houses Portal-related sub-projects.
  See the links below for getting started with each project.
  </p>
  <subsection name="Jetspeed-1">
  <p>
  <a href='jetspeed-1/GETTING-STARTED.html'>Getting Started with Jetspeed-1</a>
  </p>
  </subsection>
  <subsection name="Jetspeed-2">
  <p>
  <a href='jetspeed-2/GETTING-STARTED.html'>Getting Started with Jetspeed-2</a>
  </p>
  </subsection>
  <subsection name="Pluto">
  <p>
  <a href='pluto/GETTING-STARTED.html'>Getting Started with Pluto</a>
  </p>
  </subsection>
  <subsection name="WSRP4J">
  <p>
  <a href='wsrp4j/GETTING-STARTED.html'>Getting Started with WSRP4J</a>
  </p>
  </subsection>
  
  </section>
  
  <section name="Getting Involved">
  <p>
  This section is under construction.
  </p>
  </section>
  </body>
  </document>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
  
    <properties>
      <author email="taylor@apache.org">David Sean Taylor</author>
      <title>Apache Portals</title>
    </properties>
  
  <body>
  
  <section name="Welcome to the Apache Portals Project">
  
      <p>
      <b>Apache Portals</b> is a collaborative software development project dedicated to providing robust, 
      full-featured, commercial-quality, and freely available Portal related software on a wide variety 
      of platforms and programming languages. This project is managed in cooperation with various 
      individuals worldwide (both independent and company-affiliated experts), 
       who use the Internet to communicate, plan, and develop Portal software and related documentation.
      </p>
      <p>
        For more information on getting started with Apache Portals, see the
        <a href="getting-started.html">Getting Started</a> guide.
      </p>
      
  
  <subsection name="About Portals">
  <p>
  Modern software is complex and expensive, 
  which has motivated many companies to invest in enterprise portals as a mechanism by 
  which they can manage information in a cohesive and structured fashion.  
  </p>
  <p>
  Portals offer many advantages over other software applications.  
  First, they provide a single point of entry for employees, partners, and customers.  
  Second, portals can access Web services transparently from any device in virtually any location.   
  Third, portals are highly flexible; they can exist in the form of B2E intra-nets, B2B extra-nets, or B2C inter-nets.   
  Fourth, portals can be combined to form a portal network that can span a companys entire enterprise system, 
  allowing for access both inside and outside the firewall.
  </p>
  <p>
  Portals have many advantages, which is why they have become the de facto standard for Web application delivery.  
  In fact, analysts have predicted that portals will become the next generation for the desktop environment.   
  </p>
  <p>
  Portals distinguish themselves from other software systems because they provide the ability to integrate disparate 
  systems and leverage the functionality provided by those systems.  
  As such, they are not mutually exclusive, and do not force you into an either-or decision vis-a-vis existing software systems.  
  This point is of paramount importance, particularly when you consider the fact that Web services are destined to fuel the 
  explosion of Web applications.  Since portals can access any Web services, the conclusion is inescapable:  
  portals provide a unique opportunity to leverage the functionality of nascent technologies as well as mature, 
  well-established software systems.
  </p>
  </subsection>
  
  <subsection name="Jetspeed-1">
    <p>
      <a href="http://portals.apache.org/jetspeed-1/">Jetspeed-1</a> is an Open Source implementation of an 
      Enterprise Information Portal, using Java and XML. Jetspeed-1 is a user-customizable portal system, supporting
      a rich feature set and mature user base. 
    </p>
  </subsection>
  
  <subsection name="Jetspeed-2">
    <p>
      <a href="http://portals.apache.org/jetspeed-2/">Jetspeed-2</a> is the next-generation enterprise portal at Apache.
      Jetspeed-2 offers several architectural enhancements and improvements over Jetspeed 1.0. 
      First, Jetspeed-2 is conformant to the <a href="http://www.jcp.org/en/jsr/detail?id=168">Java Portlet Standard</a> and will provide a standard mechanism for the deployment of portlets.  
      Second, Jetspeed-2 has matured to a more scalable architecture featuring multi-threaded functionality.  
      Third, Jetspeed-2 is decoupled from several legacy open source projects.  
      Fourth, Jetspeed-2 is based on a component architecture.
    </p>
  </subsection>
  
  <subsection name="Pluto">
    <p>
    <a href="http://portals.apache.org/pluto/">Pluto</a> is the Reference Implementation of the Java Portlet Specification. 
    The current version of this Portlet specification is <a href="http://www.jcp.org/en/jsr/detail?id=168">JSR 168 1.0</a>
    Portlets are designed to run in the context of a portal. They are written to the Portlet API.
    Pluto implements the contract, the Portlet API, between portlets and portals.
    Pluto is a portlet container.
    </p>
  </subsection>
  
  <subsection name="WSRP4J">
    <p>
    <a href="http://portals.apache.org/wsrp4j/">WSRP4J</a> is the Reference Implementation of the 
    <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">Oasis WSRP Specification</a>. 
    The OASIS Web Services for Remote Portlets (WSRP) standard simplifies integration of remote applications/content into 
    portals so that portal administrators can pick from a rich choice of services and integrate it in their portal 
    without programming effort. 
    As a result, WSRP becomes the means for content and application providers to provide their services to 
    organizations running portals in a very easily consumable form.
    </p>
  </subsection>
  
  </section>
  
  </body>
  </document>
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/issue-tracking.xml
  
  Index: issue-tracking.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
  
    <properties>
      <author email="taylor@apache.org">David Sean Taylor</author>
      <title>Issue Tracking</title>
    </properties>
  
  <body>
  
  <section name="Issue Tracking">
  <p>
  Apache Portals houses Portal-related sub-projects.
  See the links below to find the issue tracking system for each sub-project.
  </p>
  <subsection name="Jetspeed-1">
  <p>
  <a href='http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10493'>Jetspeed-1 Issue Tracking</a>
  </p>
  </subsection>
  <subsection name="Jetspeed-2">
  <p>
  <a href='http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10492'>Jetspeed-2 Issue Tracking</a>
  </p>
  </subsection>
  <subsection name="Pluto">
  <p>
  <a href='http://nagoya.apache.org/bugzilla/'>Pluto Issue Tracking</a>
  </p>
  </subsection>
  <subsection name="WSRP4J">
  <p>
  <a href='http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10464'>WSRP4J Issue Tracking</a>
  </p>
  </subsection>
  
  </section>
  
  </body>
  </document>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/javadocs.xml
  
  Index: javadocs.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
  
    <properties>
      <author email="taylor@apache.org">David Sean Taylor</author>
      <title>Javadocs</title>
    </properties>
  
  <body>
  
  <section name="Javadocs">
  <p>
  Apache Portals houses Portal-related sub-projects.
  See the links below to find Javdocs for each project.
  </p>
  <subsection name="Jetspeed-1">
  <p>
  <a href='jetspeed-1/javadocs/index.html'>Javadocs for Jetspeed-1</a>
  </p>
  </subsection>
  <subsection name="Jetspeed-2">
  <p>
  <a href='jetspeed-2/javadocs/index.html'>Javadocs for Jetspeed-2</a>
  </p>
  </subsection>
  <subsection name="Pluto">
  <p>
  <a href='pluto/javadocs/index.html'>Javadocs for Pluto</a>
  </p>
  </subsection>
  <subsection name="WSRP4J">
  <p>
  <a href='pluto/javadocs/index.html'>Javadocs for WSRP4J</a>
  </p>
  </subsection>
  
  </section>
  
  <section name="Getting Involved">
  <p>
  This section is under construction.
  </p>
  </section>
  </body>
  </document>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/license.xml
  
  Index: license.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
   <properties>
    <title>Apache Software License</title>
   </properties>
  
  <body>
  <section name="Apache Software License">
  
  <pre>
                                   Apache License
                             Version 2.0, January 2004
                          http://www.apache.org/licenses/
  
     TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
  
     1. Definitions.
  
        "License" shall mean the terms and conditions for use, reproduction,
        and distribution as defined by Sections 1 through 9 of this document.
  
        "Licensor" shall mean the copyright owner or entity authorized by
        the copyright owner that is granting the License.
  
        "Legal Entity" shall mean the union of the acting entity and all
        other entities that control, are controlled by, or are under common
        control with that entity. For the purposes of this definition,
        "control" means (i) the power, direct or indirect, to cause the
        direction or management of such entity, whether by contract or
        otherwise, or (ii) ownership of fifty percent (50%) or more of the
        outstanding shares, or (iii) beneficial ownership of such entity.
  
        "You" (or "Your") shall mean an individual or Legal Entity
        exercising permissions granted by this License.
  
        "Source" form shall mean the preferred form for making modifications,
        including but not limited to software source code, documentation
        source, and configuration files.
  
        "Object" form shall mean any form resulting from mechanical
        transformation or translation of a Source form, including but
        not limited to compiled object code, generated documentation,
        and conversions to other media types.
  
        "Work" shall mean the work of authorship, whether in Source or
        Object form, made available under the License, as indicated by a
        copyright notice that is included in or attached to the work
        (an example is provided in the Appendix below).
  
        "Derivative Works" shall mean any work, whether in Source or Object
        form, that is based on (or derived from) the Work and for which the
        editorial revisions, annotations, elaborations, or other modifications
        represent, as a whole, an original work of authorship. For the purposes
        of this License, Derivative Works shall not include works that remain
        separable from, or merely link (or bind by name) to the interfaces of,
        the Work and Derivative Works thereof.
  
        "Contribution" shall mean any work of authorship, including
        the original version of the Work and any modifications or additions
        to that Work or Derivative Works thereof, that is intentionally
        submitted to Licensor for inclusion in the Work by the copyright owner
        or by an individual or Legal Entity authorized to submit on behalf of
        the copyright owner. For the purposes of this definition, "submitted"
        means any form of electronic, verbal, or written communication sent
        to the Licensor or its representatives, including but not limited to
        communication on electronic mailing lists, source code control systems,
        and issue tracking systems that are managed by, or on behalf of, the
        Licensor for the purpose of discussing and improving the Work, but
        excluding communication that is conspicuously marked or otherwise
        designated in writing by the copyright owner as "Not a Contribution."
  
        "Contributor" shall mean Licensor and any individual or Legal Entity
        on behalf of whom a Contribution has been received by Licensor and
        subsequently incorporated within the Work.
  
     2. Grant of Copyright License. Subject to the terms and conditions of
        this License, each Contributor hereby grants to You a perpetual,
        worldwide, non-exclusive, no-charge, royalty-free, irrevocable
        copyright license to reproduce, prepare Derivative Works of,
        publicly display, publicly perform, sublicense, and distribute the
        Work and such Derivative Works in Source or Object form.
  
     3. Grant of Patent License. Subject to the terms and conditions of
        this License, each Contributor hereby grants to You a perpetual,
        worldwide, non-exclusive, no-charge, royalty-free, irrevocable
        (except as stated in this section) patent license to make, have made,
        use, offer to sell, sell, import, and otherwise transfer the Work,
        where such license applies only to those patent claims licensable
        by such Contributor that are necessarily infringed by their
        Contribution(s) alone or by combination of their Contribution(s)
        with the Work to which such Contribution(s) was submitted. If You
        institute patent litigation against any entity (including a
        cross-claim or counterclaim in a lawsuit) alleging that the Work
        or a Contribution incorporated within the Work constitutes direct
        or contributory patent infringement, then any patent licenses
        granted to You under this License for that Work shall terminate
        as of the date such litigation is filed.
  
     4. Redistribution. You may reproduce and distribute copies of the
        Work or Derivative Works thereof in any medium, with or without
        modifications, and in Source or Object form, provided that You
        meet the following conditions:
  
        (a) You must give any other recipients of the Work or
            Derivative Works a copy of this License; and
  
        (b) You must cause any modified files to carry prominent notices
            stating that You changed the files; and
  
        (c) You must retain, in the Source form of any Derivative Works
            that You distribute, all copyright, patent, trademark, and
            attribution notices from the Source form of the Work,
            excluding those notices that do not pertain to any part of
            the Derivative Works; and
  
        (d) If the Work includes a "NOTICE" text file as part of its
            distribution, then any Derivative Works that You distribute must
            include a readable copy of the attribution notices contained
            within such NOTICE file, excluding those notices that do not
            pertain to any part of the Derivative Works, in at least one
            of the following places: within a NOTICE text file distributed
            as part of the Derivative Works; within the Source form or
            documentation, if provided along with the Derivative Works; or,
            within a display generated by the Derivative Works, if and
            wherever such third-party notices normally appear. The contents
            of the NOTICE file are for informational purposes only and
            do not modify the License. You may add Your own attribution
            notices within Derivative Works that You distribute, alongside
            or as an addendum to the NOTICE text from the Work, provided
            that such additional attribution notices cannot be construed
            as modifying the License.
  
        You may add Your own copyright statement to Your modifications and
        may provide additional or different license terms and conditions
        for use, reproduction, or distribution of Your modifications, or
        for any such Derivative Works as a whole, provided Your use,
        reproduction, and distribution of the Work otherwise complies with
        the conditions stated in this License.
  
     5. Submission of Contributions. Unless You explicitly state otherwise,
        any Contribution intentionally submitted for inclusion in the Work
        by You to the Licensor shall be under the terms and conditions of
        this License, without any additional terms or conditions.
        Notwithstanding the above, nothing herein shall supersede or modify
        the terms of any separate license agreement you may have executed
        with Licensor regarding such Contributions.
  
     6. Trademarks. This License does not grant permission to use the trade
        names, trademarks, service marks, or product names of the Licensor,
        except as required for reasonable and customary use in describing the
        origin of the Work and reproducing the content of the NOTICE file.
  
     7. Disclaimer of Warranty. Unless required by applicable law or
        agreed to in writing, Licensor provides the Work (and each
        Contributor provides its Contributions) on an "AS IS" BASIS,
        WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
        implied, including, without limitation, any warranties or conditions
        of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
        PARTICULAR PURPOSE. You are solely responsible for determining the
        appropriateness of using or redistributing the Work and assume any
        risks associated with Your exercise of permissions under this License.
  
     8. Limitation of Liability. In no event and under no legal theory,
        whether in tort (including negligence), contract, or otherwise,
        unless required by applicable law (such as deliberate and grossly
        negligent acts) or agreed to in writing, shall any Contributor be
        liable to You for damages, including any direct, indirect, special,
        incidental, or consequential damages of any character arising as a
        result of this License or out of the use or inability to use the
        Work (including but not limited to damages for loss of goodwill,
        work stoppage, computer failure or malfunction, or any and all
        other commercial damages or losses), even if such Contributor
        has been advised of the possibility of such damages.
  
     9. Accepting Warranty or Additional Liability. While redistributing
        the Work or Derivative Works thereof, You may choose to offer,
        and charge a fee for, acceptance of support, warranty, indemnity,
        or other liability obligations and/or rights consistent with this
        License. However, in accepting such obligations, You may act only
        on Your own behalf and on Your sole responsibility, not on behalf
        of any other Contributor, and only if You agree to indemnify,
        defend, and hold each Contributor harmless for any liability
        incurred by, or claims asserted against, such Contributor by reason
        of your accepting any such warranty or additional liability.
  
     END OF TERMS AND CONDITIONS
  
     APPENDIX: How to apply the Apache License to your work.
  
        To apply the Apache License to your work, attach the following
        boilerplate notice, with the fields enclosed by brackets "[]"
        replaced with your own identifying information. (Don't include
        the brackets!)  The text should be enclosed in the appropriate
        comment syntax for the file format. We also recommend that a
        file or class name and description of purpose be included on the
        same "printed page" as the copyright notice for easier
        identification within third-party archives.
  
     Copyright [yyyy] [name of copyright owner]
  
     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.
  </pre>
  
  </section>
  </body>
  </document>
  
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/mission.xml
  
  Index: mission.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
  
    <properties>
      <author email="taylor@apache.org">David Sean Taylor</author>
      <title>Apache Portals Mission</title>
    </properties>
  
  <body>
  <section name="Mission">
      <p>
      <b>Apache Portals</b> exists to promote the use of open source portal technology.
      We view portals as an important technology in in the growing portal and web application environments.  
      We intend to build freely available portal software in order to promote the use of this technology.
      </p>
      <p>
      To provide reference implementations Java and W3C Standards such as the
      <ul>
      <li>Java Portlet Standard (Pluto)</li>
      <li>WSRP Portlet Standard (WSRP-4J)</li>
      </ul>
      To provide portal implementations including:
      <ul>
      <li>Cocoon Portal</li>
      <li>Jetspeed-1</li>
      <li>Jetspeed-2</li>
      <li>PHP Portals (TBD)</li>
      </ul>
      To provide fully working and standardized portlet applications:
      <ul>
      <li>Jetspeed Content Replication Engine</li>
      <li>Jetspeed Portal Administration Application</li>
      <li>(TBD)</li>
      </ul>
      To provide common frameworks and tools for developing portal software
      <ul>
      <li>CPS (Cornerstone Portlet Services)</li>
      <li>Struts Portlet Application Framework</li>
      <li>Python Portlet Application Framework</li> 
      <li>Turbine Portlet Application Framework</li> 
      </ul>
      To provide portal interoperability frameworks and tools for programming languages including
      <ul>
      <li>Java</li>
      <li>Perl</li>
      <li>PHP</li>
      <li>Python</li>
      <li>...</li>
      </ul>
      </p>
  </section>
  </body>
  </document>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/navigation.xml
  
  Index: navigation.xml
  ===================================================================
  <?xml version="1.0" encoding="ISO-8859-1"?>
  <project name="Apache Portals Site"
          href="http://portals.apache.org/">
  
      <title>The Apache Portals Site</title>
  
      <body>
      <links>
        <item name="Jetspeed-1"                 href="http://jakarta.apache.org/jetspeed/"/>
        <item name="Jetspeed-2"                     href="/jetspeed-2/"/>
        <item name="Pluto"                     href="http://jakarta.apache.org/pluto/"/>
        <item name="WSRP-4J"                     href="http://ws.apache.org/wsrp4j/"/>
      </links>
  
      <menu name="About Apache Portals">
          <item name="Overview"              href="/index.html"/>
          <item name="Getting Started"       href="/getting-started.html"/>
          <item name="News and Status"       href="/news.html"/>
          <item name="Our Mission"       href="/mission.html"/>
          <item name="Portals Powered"       href="/powered.html"/>
          <item name="Supporting Organizations"       href="/supporting.html"/>
          <item name="License"               href="/license.html"/>
      </menu>
  
      <menu name="Downloads">
          <item name="Releases"        href="/download.html"/>
          <item name="CVS"              href="/cvs-usage.html"/>
          <item name="JavaDocs"              href="/javadocs.html"/>
      </menu>
  
      <menu name="Support">
          <item name="Mailing Lists"                href="/mail-lists.html"/>
          <item name="Issue Tracking"               href="/issue-tracking.html"/>
  <!--        <item name="Tutorials"                    href="/tutorials.html"/> -->
  <!--        <item name="User's Guides"                href="/guides.html"/> -->
          <item name="Wikis"                        href="/wiki.html"/>
      </menu>
  
      <menu name="Portals Sub Projects">
          <item name="Jetspeed-1"               href="http://jakarta.apache.org/jetspeed/"/>
          <item name="Jetspeed-2"                   href="/jetspeed-2/"/>
          <item name="Pluto"                   href="http://jakarta.apache.org/pluto/"/>
          <item name="WSRP-4J"                   href="http://ws.apache.org/wsrp4j/"/>
      </menu>
  
      <menu name="Development">
          <item name="Team"                href="/team-list.html"/> 
          <item name="Coding Standards"          href="/development/code-standards.html"/>
          <item name="Documentation Standards"   href="/development/documentation.html"/>
          <item name="Developer Resources"     href="/development/developer-links.html"/>
          <item name="Further Reading"         href="/development/further-reading.html"/>
      </menu>
      
      </body>
  </project>
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/news.xml
  
  Index: news.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
  
  <properties>
    <author email="taylor@apache.org">David Sean Taylor</author>
    <title>News and Status</title>
  </properties>
  
  <body>
  
  <section name="News">
  
  <h4>25 March 2004 - Apache Portals Project Launched</h4>
  <p>
  The Apache Portals project is officially launched at the Apache Software Foundation
  </p>
  
  <hr noshade="" size="1"/>
  
  </section>
  
  <section name="Status">
  
  <p>
  <a href="status/2004-03.html">March 2004 Status</a>
  </p>
  
  <hr noshade="" size="1"/>
  
  </section>
  </body>
  
  </document>
  
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/powered.xml
  
  Index: powered.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
   <properties>
    <title>Apache Portals powered web sites</title>
     <author email="taylor@apache.org">David Sean Taylor</author>
   </properties>
  
   <body>
  
   <section name="Apache Portals-Powered Web Sites">
   <p>
   <img src="images/jetspeed-powered.gif" alt="powered-by-logo.gif" width="112" height="32" />
   </p>
  
   <p>
    Here is a list of public web sites built with Apache Portals technology.
    This is by no means a complete listing of all
    of the Portals-powered web sites.  If you have a site to be listed here,
    please post a message on the Portals General List
    <a href="mailing-lists.html">mailing list</a>.
   </p>
  
   <table>
     <tr>
      <th>URL</th>
      <th>Description</th>
      <th>Projects</th>
      <th>Created By</th>
     </tr>
     <tr>
      <td>
       <a href="http://www.bluesunrise.com/jetspeed">www.bluesunrise.com</a>
      </td>
      <td>
       This site lets you see the state of the latest development on Jetspeed-1. 
       It is refreshed from the CVS Head occasionally.      
      </td>
      <td>
        Jetspeed-1
      </td>
      <td>
       <a href="http://www.bluesunrise.com/">Bluesunrise</a>
      </td>
     </tr>
     <tr>
      <td>
       <a href="http://www.mizan.com/index.jsp">www.mizan.com</a>
      </td>
      <td>
      An Indonesian publisher website that has more than 3800 members.
      </td>
      <td>
        Jetspeed-1
      </td>
      <td>
       <a href="http://www.mizan.com/">Mizan Online</a>
      </td>
     </tr>
  
    </table>
   </section>
               
   </body>
  </document>
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/supporting.xml
  
  Index: supporting.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
   <properties>
    <title>Apache Portals owered web sites</title>
     <author email="taylor@apache.org">David Sean Taylor</author>
   </properties>
  
   <body>
   <section name="Supporting Organizations">
   <p>
    The companies and organizations support and contribute to the Apache Portals projects.
   </p>
  
    <table>
     <tr>
      <th>Organization</th>
      <th>Contributions</th>
     </tr>
     <tr>
      <td>
       <a href="http://www.ibm.com/">IBM</a>
      </td>
      <td>
       Contributed reference implementations of Pluto and WSRP4J
      </td>
     </tr>
     <tr>
      <td>
       <a href="http://www.bluesunrise.com/">Bluesunrise Software</a>
      </td>
      <td>
       Apache Portal committer: David Sean Taylor
      </td>
     </tr>
    </table>
   </section>
  
   </body>
  </document>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/wiki.xml
  
  Index: wiki.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
  
    <properties>
      <author email="taylor@apache.org">David Sean Taylor</author>
      <title>Wiki</title>
    </properties>
  
  <body>
  
  <section name="Wikis">
  <p>
  Apache Portals houses Portal-related sub-projects.
  See the links below to find the Wiki for each sub-project.
  </p>
  <subsection name="Jetspeed-1">
  <p>
  <a href='http://nagoya.apache.org/wiki/apachewiki.cgi?JetspeedProjectPages'>Jetspeed-1 Wiki</a>
  </p>
  </subsection>
  <subsection name="Jetspeed-2">
  <p>
  <a href='http://nagoya.apache.org/wiki/apachewiki.cgi?JetspeedProjectPages'>Jetspeed-2 Wiki</a>
  </p>
  </subsection>
  <subsection name="Pluto">
  <p>
  <a href='http://nagoya.apache.org/wiki/apachewiki.cgi?PlutoProjectPages'>Pluto Wiki</a>
  </p>
  </subsection>
  <subsection name="WSRP4J">
  <p>
  <a href='http://nagoya.apache.org/wiki/apachewiki.cgi?WSRPProjectPages'>WSRP4J Wiki</a>
  </p>
  </subsection>
  
  </section>
  
  </body>
  </document>
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/development/code-standards.xml
  
  Index: code-standards.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
  
   <properties>
    <title>Coding Standards</title>
    <author email="taylor@apache.org">David Sean Taylor</author>
   </properties>
  
  <body>
  
  <section name="Coding Standards">
  
  <p>
  This document describes a list of coding conventions that are required
  for code submissions to the project. By default, the coding conventions
  for most Open Source Projects should follow the existing coding conventions
  in the code that you are working on. For example, if the bracket is on
  the same line as the if statement, then you should write all your code
  to have that convention.
  </p>
  
  <p>
  <strong>If you commit code that does not follow these conventions, you
  are responsible for also fixing your own code.</strong>
  </p>
  
  <p>
  Below is a list of coding conventions that are specific to Apache Portals,
  everything else not specificially mentioned here should follow the official
  <a href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Sun
  Java Coding Conventions</a>.
  </p>
  
  <p>
  1. Brackets should begin and end on a new line and should exist even
  for one line statements. Examples:
  </p>
  
  <source test=""><![CDATA[
  if (foo)
  {
      // code here
  }
  
  try
  {
      // code here
  }
  catch (Exception bar)
  {
      // code here
  }
  finally
  {
      // code here
  }
  
  while (someCondition)
  {
      // code here
  }
  ]]></source>
  
  <p>
  2. Though it's considered okay to include spaces inside parens, the
  preference is to not include them. Both of the following are okay:
  </p>
  
  <source test=""><![CDATA[
  if (foo)
  
  or
  
  if ( foo )
  ]]></source>
  
  <p>
  3. 4 space indent. <strong>NO tabs</strong>. Period. We understand
  that many developers like to use tabs, but the fact of the matter is
  that in a distributed development environment where diffs are sent to
  the mailing lists by both developers and the version control system
  (which sends commit log messages), the use tabs makes it impossible to
  preserve legibility.
  </p>
  
  <p>
  In Emacs-speak, this translates to the following command:
  </p>
  
  <source><![CDATA[
  (setq-default tab-width 4 indent-tabs-mode nil)
  ]]></source>
  
  <p>
  4. Unix linefeeds for all .java source code files. Other platform specific
  files should have the platform specific linefeeds.
  </p>
  
  <p>
  5. JavaDoc <strong>MUST</strong> exist on all methods.  If your code
  modifications use an existing class/method/variable which lacks
  JavaDoc, it is required that you add it.  This will improve the
  project as a whole.  For guidelines on how to write proper
  JavaDocs, see 
  <a href="http://java.sun.com/j2se/javadoc/writingdoccomments/index.html">
  Sun's guidelines</a>
  </p>
  
  <p>
  6. When writing javadocs for variables, try to keep the comment on just
  one line.  
  </p>
  <source><![CDATA[
  /** Documentation of this variable */
  private int myVariable;
  
  /**
   * If the documentation of the variable is enough to occupy multiple
   * lines, then this form of comment is also perfectly acceptable.
   */
  private int myVariable;
  ]]></source>
  
  <p>
  7. The Apache License <strong>MUST</strong> be placed at the top
  of each and every file.
  </p>
  
  <p>
  8. If you contribute to a file (code or documentation), add yourself to the
  authors list at the top of the file. You should add yourself to the end of
  the list of authors.  For java files the preferred Javadoc format is:
  </p>
  
  <source><![CDATA[
  @author <a href="mailto:user@domain.com">John Doe</a>
  ]]></source>
  
  <p>
  9. All .java files should have a @version tag like the one below.
  </p>
  
  <source><![CDATA[
  @version $Id: code-standards.xml,v 1.1 2004/03/26 00:18:16 taylor Exp $
  ]]></source>
  
  <p>
  10. Import statements must be fully qualified for clarity.
  </p>
  
  <source><![CDATA[
  import java.util.ArrayList;
  import java.util.Hashtable;
  
  import org.apache.foo.Bar;
  import org.apache.bar.Foo;
  ]]></source>
  
  <p>
  And not
  </p>
  
  <source><![CDATA[
  import java.util.*;
  import org.apache.foo.*;
  import org.apache.bar.*;
  ]]></source>
  
  <p>
  11. Import statements should be listed in alphabetical order.  Use blank lines 
  to seperate products.  In cases where there is a large number of imports from a 
  single product (like java.x) consider seperating at the second level.  For example,
  you could group all of the java.util, java.swing, etc...
  </p>
  
  <p>
  12.  The conditional part of if and while statements should not use 
  the equality operator for testing true or false values.  
  </p>
  
  <source test=""><![CDATA[
  if (foo)
  
  and not
  
  if (foo==true)
  ]]></source>
  
  <p>
  13.  Always use the short form of the classname in code.  Certain exception
  do apply where the fully qualified classname is required such as when 
  java.sql.Date and java.util.Date are used in the same class.  Otherwise, you
  should always import the class and use the short name.
  </p>
  
  <source test=""><![CDATA[
  try
  {
  }
  catch (IOException e)
  {
  }
  
  and not
  
  try
  {
  }
  catch (java.io.IOException e)
  {
  }
  ]]></source>
  
  <p>
  14.  Avoid using Iterators that are initialized outside of the loop.
  </p>
  
  <source test=""><![CDATA[
  for (Iterator iter=getIterator(); iter.hasNext; )
  {
  }
  
  and not
  
  Iterator iter=getIterator();
  for (;iter.hasNext; )
  {
  }
  ]]></source>
  
  <hr noshade="true" size="1"/>
  
  <p>
  X/Emacs users might appreciate this in their .emacs file.
  </p>
  
  <source><![CDATA[
  (defun apache-jakarta-mode ()
    "The Java mode specialization for Apache Jakarta projects."
    (if (not (assoc "apache-jakarta" c-style-alist))
        ;; Define the Apache Jakarta cc-mode style.
        (c-add-style "apache-jakarta" '("java" (indent-tabs-mode . nil))))
  
    (c-set-style "apache-jakarta")
    (c-set-offset 'substatement-open 0 nil)
    (setq mode-name "Apache Jakarta")
  
    ;; Turn on syntax highlighting when X is running.
    (if (boundp 'window-system)
        (progn (setq font-lock-support-mode 'lazy-lock-mode)
               (font-lock-mode t))))
  
  ;; Activate Jakarta mode.
  (if (fboundp 'jde-mode)
      (add-hook 'jde-mode-hook 'apache-jakarta-mode)
    (add-hook 'java-mode-hook 'apache-jakarta-mode))
  ]]></source>
  
  <p>
  Thanks for your cooperation.
  </p>
  
  
  </section>
  
  </body>
  </document>
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/development/developer-links.xml
  
  Index: developer-links.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
  
   <properties>
    <title>Developer Links</title>
    <author email="taylor@apache.org">David Sean Taylor</author>
   </properties>
  
  <body>
  
  <section name="Developer Links">
  
  <p>
  This document contains links that can aid you in the development of turbine
  </p>
  
  <ul>
  <li>Portlet API Specs: 
    <a href="http://www.bluesunrise.com/portlet-api/index.html"><b>Portlet API 1.0 Javadocs</b></a>, 
    <a href="http://www.jcp.org/en/jsr/detail?id=168"><b>Portlet API Home</b></a>
  </li>
  
  <li>WSRP: 
    <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp"><b>WSRP Home</b></a>
  </li>
  
  <li>Servlet Specs: 
    <a href="http://java.sun.com/cgi-bin/download3.cgi?config-file=servlet2_2-spec.config&amp;platform=pdf&amp;type=spec&amp;button=continue"><b>2.2</b></a>, 
    <a href="http://java.sun.com/Download4?config-file=servlet-2_3-pfd2-spec.config&amp;platform=pdf&amp;type=spec&amp;button=Continue"><b>2.3</b></a>
  </li>
  <li>Servlet API: 
    <a href="http://java.sun.com/products/servlet/2.2/javadoc/"><b>2.2</b></a>, 
    <a href="http://java.sun.com/products/servlet/2.3/javadoc/"><b>2.3</b></a>
  </li>
  
  <li>Servlet Deltas: 
    <a href="http://www.servlets.com/soapbox/servlet22.html"><b>2.1-&gt;2.2</b></a>, 
    <a href="http://www.servlets.com/soapbox/servlet23.html"><b>2.2-&gt;2.3</b></a></li>
  <li>HTTP RFCs: 
  <b><a href="http://www.servlets.com/rfcs/rfc1945.txt">1.0</a></b>, 
  <b><a href="http://www.servlets.com/rfcs/rfc2616.txt">1.1</a></b>
  </li>
  <li>File Upload RFCs: 
  	<a href="http://www.servlets.com/rfcs/rfc1867.txt"><b>1867</b></a>, 
  	<b><a href="http://www.servlets.com/rfcs/rfc2388.txt">2388</a></b></li>
  <li>HTML Specs: 
  <b><a href="http://www.w3.org/TR/REC-html32">3.2</a></b>, 
  <b><a href="http://www.w3.org/TR/html4/">4.0</a></b>
  </li>
  <li>Cookie Specs: 
  <a href="http://home.netscape.com/newsref/std/cookie_spec.html"><b>Netscape</b></a>, 
  <b><a href="http://www.servlets.com/rfcs/rfc2109.txt">2109</a></b>
  </li>
  </ul>
  
  <p>
  Be free to add your own links.
  </p>
  
  </section>
  
  </body>
  </document>
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/development/documentation.xml
  
  Index: documentation.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
  
   <properties>
    <title>The Apache Portals Documentation Effort</title>
    <author email="taylor@apache.org">David Sean Taylor</author>
    </properties>
  
  <body>
  
  <section name="The Apache Portals Documentation Effort">
  
    <subsection name="Documentation Roadmap">
  <p>
        This page covers how to contribute to the Apache Portals's documentation.
        We are working very hard to improve Apache Portals's documentation.  
  </p>
  
  <p>
        Below is the list of documentation items we are working on listed in order
        of priority from greatest to lowest.  We need help with them all!
  </p>
  
  <ul>
        <li>
          <b>Apache Portals Website</b>
          <ul>The Portals website needs work..</ul>
        </li>
        <li>
          <b>Jetspeed-2 Website</b>
          <UL>
          <li>The Jetspeed-2 Website needs a lot of work</li>
          <li>Each component needs its own documentation page</li>
          </UL>
        </li>
        <li>
          <b>Jetspeed-1 Website Conversion</b>
          <UL>
          <li>Jetspeed-1 Website needs to be converted to Maven</li>
          <li>Add tutorial from Bluesunrise</li>
          </UL>
        </li>
  </ul>
    </subsection>
    
    <subsection name="Our Documentation Has Three States">
      <ol>
        <li>
          <strong>Infancy:</strong>  A document becomes nascent in the Wiki
          as an empty or sparsely populated page.  At this point, people continue to
          add and revise the content until it becomes mostly stable and unchanging.
          <ul><!-- FOR SPACING --></ul>
        </li>
        <li>
          <strong>Stability:</strong>  Once the document has reached a stable point, it is converted into the xdoc
          format and injected into the portals-site (or subproject) cvs modules.
          <ul><!-- FOR SPACING --></ul>
        </li>
        <li>
          <strong>Maturity:</strong>   As changes to the projects are made, the documentation
          is updated and improved via xdoc patches from the <a href="../issue-tracking.html">Issue Tracking system</a>.
          <ul><!-- FOR SPACING --></ul>
        </li>
      </ol>
    </subsection>
  
    <subsection name="How You Can Help">
  <p>
        Now that you know what we are working on, you need to know the best ways to help.
        Content is farmed and stabilized on the <a href="../wiki.html">Apache Portals Wikis</a>
        until it is stable enough to become official documentation.  Additionally 
        questions are answered and re-answered on the mailing lists.  
        You can help the Documentation effort by:
  </p>
  <ul>
        <li>
          <strong>Editing The Wiki Content:</strong> Mature and stabilize the information on the <a href="wiki.html">Wiki</a>.
          <ul><!-- FOR SPACING --></ul>
        </li>
        <li>
          <strong>Filtering The Mailing List:</strong> When you see something float
          by on the mailing list that should become part of the official,
          please convert it into the appropriate xdoc format and submit it as an
          issue in our <a href="../issue-tracking.html">Issue Tracking system</a>.
          <ul><!-- FOR SPACING --></ul>
        </li>
        <li>
          <strong>Creating Xdoc Patches:</strong> If you find a typo, mistake or
          overlooked information in the official documentation, please create
          an issue in our <a href="../issue-tracking.html">Issue Tracking system</a>.
          <ul><!-- FOR SPACING --></ul>
  </li>
  </ul>
    </subsection>
  
    <subsection name="Getting The Documentation Source And Making A Patch">
      <ol>
        <li>
  <p>
            <strong>Get The Source:</strong>
            Check out the latest source from the Portals CVS module.  You can learn
            about the CVS repositories <a href="../cvs-usage.html">here</a>.
            The Portals Site documentation resides in the portals-site module:
  </p>
          <source><![CDATA[cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login
  password: anoncvs
  cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic checkout portals-site]]></source>
        </li>
        <li>
  <p>
            <strong>Build The Site:</strong>
            The documenation is built using <a href="http://maven.apache.org/">Maven</a>,
            with the following command:
  </p>
          <source><![CDATA[maven site:generate]]></source>
  
  <p>
            Afterwards, you should get something like:
  </p>
          <source><![CDATA[BUILD SUCCESSFUL
  Total time:  20 seconds]]></source>
  
  <p>
            You will find the built HTML in $PATH_TO_MODULE/target/docs.
  </p>
        </li>
  
        <li>
          <strong>Make Your Changes:</strong>
          The docs are written using the Anakia Xdoc format, which you can learn about <a href="http://jakarta.apache.org/site/jakarta-site-tags.html">here</a>.
          The source files are found in the $PATH_TO_MODULE/xdocs directory, each xml file corresponding to the generated html file.
          Menu information is found in the navigation.xml files.
          <ul><!-- FOR SPACING --></ul>
        </li>
  
        <li>
          <strong>Make A Patch:</strong>
          <source><![CDATA[cvs diff -rNu > name_of_patch.patch]]></source>
          <ul><!-- FOR SPACING --></ul>
        </li>
  
        <li>
          <strong>Submit Your Changes:</strong>
          We use the <a href="../issue-tracking.html">JIRA Issue Tracking system</a> to track issues.  Once
          you have a patch, log in the Issue Tracking System
          and create a new issue in the Documentation module.  A project committer will approve the patch
          and apply it, or let you know if something should be changed.
          <ul><!-- FOR SPACING --></ul>
        </li>
  
        <li><strong>Thank you for helping out!</strong></li>
      </ol>
    </subsection>
  </section>
  
  </body>
  </document>
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/development/further-reading.xml
  
  Index: further-reading.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
  
   <properties>
    <title>Further Reading</title>
    <author email="taylor@apache.org">David Sean Taylor</author>
   </properties>
  
  <body>
  
  <section name="Related Jakarta Apache Projects">
  
  <p>
    <a href="http://jakarta.apache.org/velocity">Velocity</a> is a view 
    technology comparable to JSP) that Apache Portals officially supports. Many 
    portlet developers feel Velocity is an excellent alternative
    to JSP for web application development.
  </p>
    
  <p>
    Portals uses <a href="http://jakarta.apache.org/log4j">Log4j</a> for a 
    logging framework.  No more commenting System.out.println()'s in your code!
  </p>
   
  <p>
    <a href="http://maven.apache.org/">Maven</a> is a Java 
    project management and project comprehension tool. Maven is based on the 
    concept of a project object model (POM) in that all the artifacts produced 
    by Maven are a result of consulting a well defined model for your project.
  </p>
     
  </section>
   
  <section name="Articles on Apache Portals and related projects">
   
  <p>
    <a href="http://www.javaworld.com/javaworld/jw-10-2002/jw-1011-maven.html">
    Maven article</a> - Maven ties together tools for better code management.
    by Jeff Linwood, published in JavaWorld on October 11, 2002.
  </p>
   
  <p>
    <a href="http://www.javaworld.com/javaworld/jw-12-2001/jw-1228-velocity.html">
    Velocity Introduction</a> - Start up the Velocity Template Engine.
    by Geir Magnusson, Jr., published in JavaWorld on December 28, 2001.
  </p>
   
  </section>
   
  <section name="Related Links">
  <p>
    The web application framework comparison project 
    <a href="http://www.waferproject.org/index.html">WAFER</a> takes a look at
    the many web application frameworks available and 
    makes a comparison.
  </p>
  </section>
   
  <section name="Viewpoints on JSP">
   
  <p>
    On the Velocity site, there is Jon Stevens'
    <a href="http://jakarta.apache.org/velocity/ymtd/ymtd.html">
    You Make The Decision</a>, which compares Velocity to JSP.
   .
  </p>
  
  <p>
    Then there is Jason Hunter's
    <a href="http://www.servlets.com/soapbox/problems-jsp.html">
    Problems with JSP</a>.
  </p>
  
  </section>
  
  </body>
  </document>
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/images/apache-portals-2.gif
  
  	<<Binary file>>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/images/apache-portals-big.gif
  
  	<<Binary file>>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/images/apache-portals-bw.gif
  
  	<<Binary file>>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/images/apache-portals.gif
  
  	<<Binary file>>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/images/apache.gif
  
  	<<Binary file>>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/images/jetspeed-powered.gif
  
  	<<Binary file>>
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/xdocs/status/2004-03.xml
  
  Index: 2004-03.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
  
    <properties>
      <title>Apache Portals</title>
      <author email="taylor@apache.org">David Sean Taylor</author>
    </properties>
  
    <body>
  
    <section name="Monthly Status Report: March 2004">
  
    <subsection name="Apache Portals">
       <p>
       We are creating the Apache Portals websites, issue logging, mailing lists, CVS.     
       </p>
     </subsection>
  
     <subsection name="Pluto">
       <p>
       Pluto needs to graduate from incubator!
       </p>
     </subsection>
  
     <subsection name="Jetspeed-1">
       <p>
       Working towards release 1.5 this month.
       </p>
     </subsection>
  
     <subsection name="Jetspeed-2">
       <p>
       Code, code, code....developing core components, and converting over from
       Fulcrum services to IoC Pico Components and Containers.
       We are finally starting to write portlets.
       </p>
     </subsection>
  
     <subsection name="WSRP-4J">
       <p>
       </p>
     </subsection>
  
     </section>
  
    </body>
  </document>
  
  
  

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


Mime
View raw message