You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by hu...@apache.org on 2006/02/10 21:58:36 UTC
svn commit: r376838 [2/6] - in /struts/site/trunk/xdocs: announce.xml
bylaws.xml download.xml downloads.xml faqs.xml helping.xml index.xml
javadoc.xml kickstart.xml mail.xml navigation.xml release-checklist.xml
releases.xml struts.css volunteers.xml
Modified: struts/site/trunk/xdocs/bylaws.xml
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/bylaws.xml?rev=376838&r1=376837&r2=376838&view=diff
==============================================================================
--- struts/site/trunk/xdocs/bylaws.xml (original)
+++ struts/site/trunk/xdocs/bylaws.xml Fri Feb 10 12:58:33 2006
@@ -18,307 +18,425 @@
-->
<document>
- <properties>
- <title>Project Management Committee Charter</title>
- </properties>
-
-<body>
-
-<section name="Apache Struts PMC Charter">
-
- <p>
- Struts is a Project of the <a href="http://apache.org/foundation">
- Apache Software Foundation</a> (ASF), formed by a resolution of the
- <a href="http://apache.org/foundation/board/">ASF Board of
- Directors</a>. As an ASF Project, Struts is subject to the
- <a href="http://apache.org/foundation/bylaws.html">ASF Bylaws</a>
- and the direction of the ASF Board.
- </p>
-
- <subsection name="Roles and Responsibilities">
-
- <p>
- The roles and responsibilities that people can assume in the project
- are based on merit. Everybody can help no matter what their role.
- Those who have been longterm or valuable contributors to the project
- can earn the right to commit directly to the source repository and to
- cast binding votes during the decision-making process.
- </p>
-
- <p>
- <strong>Users.</strong>
- Users are the people who use the products of the Project. People in
- this role aren't contributing code, but they are using the products,
- reporting bugs, making feature requests, and such. This is by far
- the most important category of people as, without users, there is no
- reason for the Project. When a user starts to contribute code or
- documentation patches, they become a Contributor.
- </p>
-
- <p>
- <strong>Contributors.</strong>
- Contributors are the people who write code or documentation patches or
- contribute positively to the project in other ways. When a volunteer's
- patch is applied, the contribution is recognized in the version control
- log.
- </p>
-
- <p>
- <strong>Committers.</strong>
- Contributors who give frequent and valuable contributions to a
- subproject of the Project can have their status promoted to that of
- a "<em>Committer</em>" for that subproject. A Committer
- has write access to the source code repository. Committer status is
- granted by the Project Management Committee by majority vote.
- </p>
-
- <p>
- <strong>Project Management Committee (PMC).</strong>
- Committers and other volunteers who frequently participate with
- valuable contributions may have their status promoted to that of a
- "<em>Project Management Committee Member</em>". The PMC
- is responsible for the day-to-day management of the Project.
- </p>
-
- </subsection>
-
- <subsection name="Management">
-
- <p>
- The Vice President is appointed by the ASF Board. The Vice
- President is assisted by the Project Management Committee (PMC)
- and also serves as the PMC chair. The PMC may nominate new
- members. Nominees may then be approved with a 3/4 majority vote
- of the PMC. Membership can be revoked by a unanimous vote of all
- the active PMC members other than the member in question. The
- list of active PMC members can be found on our
- <a href="volunteers.html">Volunteers page</a>.
- </p>
-
- </subsection>
-
- <subsection name="PMC Duties">
-
- <p>
- The PMC is responsible for the day-to-day
- management of the Struts Project. The PMC oversees all changes
- made to the codebase. The PMC must ensure that all code under a
- Apache Struts repository is the lawful property of the Foundation and
- may be distributed under the <a href="http://apache.org/licenses/">
- Apache Software License</a>. All releases of a Struts subproject
- must be sanctioned by the Project Management Committee.
- </p>
-
- </subsection>
-
- <subsection name="Subprojects">
-
- <p>
- Subprojects are the Project's unit of release. Each subproject should
- represent an implementation of a Struts framework or a related component.
- Each subproject should focus on creating, maintaining, and releasing a
- single software product or "deliverable".
- </p>
-
- <p>
- All PMC Members have voting rights in all subprojects. Members not familiar
- with a subproject codebase may abstain from any given vote. All Committers
- have write access to all subprojects. Subprojects are units of release, not
- units of work.
- </p>
-
- <p>
- PMC members may propose the creation of new subprojects. Proposals are
- to contain the scope of the project, identify the initial source from
- which the project is to be populated, identify any mailing lists or
- repositories, if any, which are to be created. Creation of a new
- subproject requires approval by a 3/4 majority vote of the PMC.
- </p>
-
- </subsection>
-
- <subsection name="Decision Making">
-
- <p>
- All Volunteers are encouraged to participate in decisions, but the
- decision itself is made by the Project Management Committee.
- The Project is a "<em>Minimum Threshold Meritocracy</em>".
- </p>
-
- </subsection>
-
- <subsection name="Voting">
-
- <p>
- Any subscriber to the list may vote on any issue or action item.
- Votes from Contributors and Committers are especially welcome.
- However, the only binding votes are those cast by a PMC Member.
- </p>
-
- <p>
- The act of voting carries certain obligations. Voters are not only
- stating their opinion, they are also agreeing to help do the work.
- </p>
-
- <p>Each vote can be made in one of three flavors:</p>
-
- <table>
- <tr>
- <td><strong>+1</strong></td>
- <td>
- "Yes," "Agree," or "the action should be
- performed." On some issues this is only binding if the voter
- has tested the action on their own system(s).
- </td>
- </tr>
-
- <tr>
- <td><strong>+/-0</strong></td>
- <td>
- "Abstain," "no opinion". An abstention may
- have detrimental effects if too many people abstain.
- </td>
- </tr>
-
- <tr>
- <td><strong>-1</strong></td>
- <td>
- <p>
- "No." On issues where consensus is required, this vote
- counts as a <strong>veto</strong>. All vetos must contain an
- explanation of why the veto is appropriate. Vetos with no
- explanation are void. A veto cannot be overruled. If you disagree
- with the veto, you should lobby the person who cast the veto.
- Voters intending to veto an action item should make their opinions
- known to the group immediately so that the problem can be remedied
- as early as possible.
- </p>
- <p>
- If a Committer tries to "override" a veto by restoring a vetoed
- change, the PMC may ask the infrastructure team to revoke that
- Committer's write privileges.
- </p>
- </td>
- </tr>
-
- </table>
-
- <p>
- An action requiring consensus approval must receive at least
- <strong>3 binding +1</strong> votes and <strong>no binding
- vetos</strong>. An action requiring majority approval must receive
- at least <strong>3 binding +1</strong> votes and more
- <strong>+1</strong> votes than <strong>-1</strong> votes. All other
- action items are considered to have lazy approval until somebody
- votes <strong>-1</strong>, after which point they are decided by
- either consensus or majority vote, depending on the type of action
- item.
- </p>
- <p>
- Voting represent consensus and votes are never final. Circumstances
- change, and so may votes. A veto may be converted to a +1 after
- discussion, and likewise a +1 may be converted to a -1.
- By convention, Committers should allow a vote to circulate for 72
- hours before taking action.
- </p>
- </subsection>
-
- <subsection name="Action Items">
-
- <p>
- All decisions revolve around "<em>Action
- Items.</em>" Action Items consist of the following:
- </p>
-
- <ul>
- <li>Long Term Plans</li>
- <li>Short Term Plans</li>
- <li>Product Changes</li>
- <li>Showstoppers</li>
- <li>Release Plan</li>
- <li>Release Grade</li>
- </ul>
-
- </subsection>
-
- <subsection name="Long Term Plans">
-
- <p>
- Long term plans are simply announcements that group members are
- working on particular issues related to the Project. These are not
- voted on, but Committers and PMC Members who do not agree with a
- particular plan, or think that an alternative plan would be better,
- are obligated to inform the group of their feelings.
- </p>
-
- </subsection>
-
- <subsection name="Short Term Plan">
-
- <p>
- Short term plans are announcements that a volunteer is working on a
- particular set of documentation or code files with the implication
- that other volunteers should avoid them or try to coordinate their
- changes.
- </p>
-
- </subsection>
-
- <subsection name="Product Changes">
-
- <p>
- All product changes to the repository are subject to
- lazy consensus.
- </p>
-
- </subsection>
-
- <subsection name="Showstoppers">
-
- <p>
- Showstoppers are issues that require a fix be in place before the
- next public release. They are listed in the status file in order to
- focus special attention on these problems. An issue becomes a
- showstopper when it is listed as such in the status file and remains
- so by lazy consensus.
- </p>
-
- </subsection>
-
- <subsection name="Release Plan">
-
- <p>
- A release plan must be used to keep all volunteers aware of when a
- release is desired, whether it will be a major, minor, or
- milestone release, who will be the release manager, when the
- repository will be tagged to create the distribution, and other assorted
- information to keep volunteers from tripping over each other. A release
- plan must be announced to the DEV list. Lazy majority decides each issue
- in a release plan.
- </p>
-
- </subsection>
-
- <subsection name="Release Grade">
-
- <p>
- After a proposed release is built, it must be tested and classified before
- being released to the general public. The proposed release may be assigned
- "Alpha", "Beta" or "General Availability" classifications by majority vote.
- Once a release is classified by the PMC Members, it may be distributed to
- the general public on behalf of the Foundation. Distributions may be
- reclassified or withdrawn by majority vote, but the release number may not
- be reused by another distribution.
- </p>
-
- </subsection>
-</section>
-
- <section>
- <p class="right">
- Next: <a href="releases.html">Release Guidelines</a>
- </p>
- </section>
+ <properties>
+ <title>Project Management Committee Charter</title>
+ </properties>
+
+ <body>
+
+ <section name="Apache Struts PMC Charter">
+
+ <p>
+ Struts is a Project of the
+ <a href="http://apache.org/foundation">
+ Apache Software Foundation</a>
+ (ASF), formed by a resolution of the
+ <a href="http://apache.org/foundation/board/">ASF Board of
+ Directors</a>
+ . As an ASF Project, Struts is subject to the
+ <a href="http://apache.org/foundation/bylaws.html">ASF
+ Bylaws</a>
+ and the direction of the ASF Board.
+ </p>
+
+ <subsection name="Roles and Responsibilities">
+
+ <p>
+ The roles and responsibilities that people can assume in
+ the project
+ are based on merit. Everybody can help no matter what
+ their role.
+ Those who have been longterm or valuable contributors to
+ the project
+ can earn the right to commit directly to the source
+ repository and to
+ cast binding votes during the decision-making process.
+ </p>
+
+ <p>
+ <strong>Users.</strong>
+ Users are the people who use the products of the Project.
+ People in
+ this role aren't contributing code, but they are using the
+ products,
+ reporting bugs, making feature requests, and such. This is
+ by far
+ the most important category of people as, without users,
+ there is no
+ reason for the Project. When a user starts to contribute
+ code or
+ documentation patches, they become a Contributor.
+ </p>
+
+ <p>
+ <strong>Contributors.</strong>
+ Contributors are the people who write code or
+ documentation patches or
+ contribute positively to the project in other ways. When a
+ volunteer's
+ patch is applied, the contribution is recognized in the
+ version control
+ log.
+ </p>
+
+ <p>
+ <strong>Committers.</strong>
+ Contributors who give frequent and valuable contributions
+ to a
+ subproject of the Project can have their status promoted
+ to that of
+ a "
+ <em>Committer</em>
+ " for that subproject. A Committer
+ has write access to the source code repository. Committer
+ status is
+ granted by the Project Management Committee by majority
+ vote.
+ </p>
+
+ <p>
+ <strong>Project Management Committee (PMC).</strong>
+ Committers and other volunteers who frequently participate
+ with
+ valuable contributions may have their status promoted to
+ that of a
+ "
+ <em>Project Management Committee Member</em>
+ ". The PMC
+ is responsible for the day-to-day management of the
+ Project.
+ </p>
+
+ </subsection>
+
+ <subsection name="Management">
+
+ <p>
+ The Vice President is appointed by the ASF Board. The Vice
+ President is assisted by the Project Management Committee
+ (PMC)
+ and also serves as the PMC chair. The PMC may nominate new
+ members. Nominees may then be approved with a 3/4 majority
+ vote
+ of the PMC. Membership can be revoked by a unanimous vote
+ of all
+ the active PMC members other than the member in question.
+ The
+ list of active PMC members can be found on our
+ <a href="volunteers.html">Volunteers page</a>
+ .
+ </p>
+
+ </subsection>
+
+ <subsection name="PMC Duties">
+
+ <p>
+ The PMC is responsible for the day-to-day
+ management of the Struts Project. The PMC oversees all
+ changes
+ made to the codebase. The PMC must ensure that all code
+ under a
+ Apache Struts repository is the lawful property of the
+ Foundation and
+ may be distributed under the
+ <a href="http://apache.org/licenses/">
+ Apache Software License</a>
+ . All releases of a Struts subproject
+ must be sanctioned by the Project Management Committee.
+ </p>
+
+ </subsection>
+
+ <subsection name="Subprojects">
+
+ <p>
+ Subprojects are the Project's unit of release. Each
+ subproject should
+ represent an implementation of a Struts framework or a
+ related component.
+ Each subproject should focus on creating, maintaining, and
+ releasing a
+ single software product or "deliverable".
+ </p>
+
+ <p>
+ All PMC Members have voting rights in all subprojects.
+ Members not familiar
+ with a subproject codebase may abstain from any given
+ vote. All Committers
+ have write access to all subprojects. Subprojects are
+ units of release, not
+ units of work.
+ </p>
+
+ <p>
+ PMC members may propose the creation of new subprojects.
+ Proposals are
+ to contain the scope of the project, identify the initial
+ source from
+ which the project is to be populated, identify any mailing
+ lists or
+ repositories, if any, which are to be created. Creation of
+ a new
+ subproject requires approval by a 3/4 majority vote of the
+ PMC.
+ </p>
+
+ </subsection>
+
+ <subsection name="Decision Making">
+
+ <p>
+ All Volunteers are encouraged to participate in decisions,
+ but the
+ decision itself is made by the Project Management
+ Committee.
+ The Project is a "
+ <em>Minimum Threshold Meritocracy</em>
+ ".
+ </p>
+
+ </subsection>
+
+ <subsection name="Voting">
+
+ <p>
+ Any subscriber to the list may vote on any issue or action
+ item.
+ Votes from Contributors and Committers are especially
+ welcome.
+ However, the only binding votes are those cast by a PMC
+ Member.
+ </p>
+
+ <p>
+ The act of voting carries certain obligations. Voters are
+ not only
+ stating their opinion, they are also agreeing to help do
+ the work.
+ </p>
+
+ <p>Each vote can be made in one of three flavors:</p>
+
+ <table>
+ <tr>
+ <td>
+ <strong>+1</strong>
+ </td>
+ <td>
+ "Yes," "Agree," or "the
+ action should be
+ performed." On some issues this is only
+ binding if the voter
+ has tested the action on their own system(s).
+ </td>
+ </tr>
+
+ <tr>
+ <td>
+ <strong>+/-0</strong>
+ </td>
+ <td>
+ "Abstain," "no opinion". An
+ abstention may
+ have detrimental effects if too many people
+ abstain.
+ </td>
+ </tr>
+
+ <tr>
+ <td>
+ <strong>-1</strong>
+ </td>
+ <td>
+ <p>
+ "No." On issues where consensus is
+ required, this vote
+ counts as a
+ <strong>veto</strong>
+ . All vetos must contain an
+ explanation of why the veto is appropriate.
+ Vetos with no
+ explanation are void. A veto cannot be
+ overruled. If you disagree
+ with the veto, you should lobby the person who
+ cast the veto.
+ Voters intending to veto an action item should
+ make their opinions
+ known to the group immediately so that the
+ problem can be remedied
+ as early as possible.
+ </p>
+ <p>
+ If a Committer tries to "override" a veto by
+ restoring a vetoed
+ change, the PMC may ask the infrastructure
+ team to revoke that
+ Committer's write privileges.
+ </p>
+ </td>
+ </tr>
+
+ </table>
+
+ <p>
+ An action requiring consensus approval must receive at
+ least
+ <strong>3 binding +1</strong>
+ votes and
+ <strong>no binding
+ vetos</strong>
+ . An action requiring majority approval must receive
+ at least
+ <strong>3 binding +1</strong>
+ votes and more
+ <strong>+1</strong>
+ votes than
+ <strong>-1</strong>
+ votes. All other
+ action items are considered to have lazy approval until
+ somebody
+ votes
+ <strong>-1</strong>
+ , after which point they are decided by
+ either consensus or majority vote, depending on the type
+ of action
+ item.
+ </p>
+ <p>
+ Voting represent consensus and votes are never final.
+ Circumstances
+ change, and so may votes. A veto may be converted to a +1
+ after
+ discussion, and likewise a +1 may be converted to a -1.
+ By convention, Committers should allow a vote to circulate
+ for 72
+ hours before taking action.
+ </p>
+ </subsection>
+
+ <subsection name="Action Items">
+
+ <p>
+ All decisions revolve around "
+ <em>Action
+ Items.</em>
+ " Action Items consist of the following:
+ </p>
+
+ <ul>
+ <li>Long Term Plans</li>
+ <li>Short Term Plans</li>
+ <li>Product Changes</li>
+ <li>Showstoppers</li>
+ <li>Release Plan</li>
+ <li>Release Grade</li>
+ </ul>
+
+ </subsection>
+
+ <subsection name="Long Term Plans">
+
+ <p>
+ Long term plans are simply announcements that group
+ members are
+ working on particular issues related to the Project. These
+ are not
+ voted on, but Committers and PMC Members who do not agree
+ with a
+ particular plan, or think that an alternative plan would
+ be better,
+ are obligated to inform the group of their feelings.
+ </p>
+
+ </subsection>
+
+ <subsection name="Short Term Plan">
+
+ <p>
+ Short term plans are announcements that a volunteer is
+ working on a
+ particular set of documentation or code files with the
+ implication
+ that other volunteers should avoid them or try to
+ coordinate their
+ changes.
+ </p>
+
+ </subsection>
+
+ <subsection name="Product Changes">
+
+ <p>
+ All product changes to the repository are subject to
+ lazy consensus.
+ </p>
+
+ </subsection>
+
+ <subsection name="Showstoppers">
+
+ <p>
+ Showstoppers are issues that require a fix be in place
+ before the
+ next public release. They are listed in the status file in
+ order to
+ focus special attention on these problems. An issue
+ becomes a
+ showstopper when it is listed as such in the status file
+ and remains
+ so by lazy consensus.
+ </p>
+
+ </subsection>
+
+ <subsection name="Release Plan">
+
+ <p>
+ A release plan must be used to keep all volunteers aware
+ of when a
+ release is desired, whether it will be a major, minor, or
+ milestone release, who will be the release manager, when
+ the
+ repository will be tagged to create the distribution, and
+ other assorted
+ information to keep volunteers from tripping over each
+ other. A release
+ plan must be announced to the DEV list. Lazy majority
+ decides each issue
+ in a release plan.
+ </p>
+
+ </subsection>
+
+ <subsection name="Release Grade">
+
+ <p>
+ After a proposed release is built, it must be tested and
+ classified before
+ being released to the general public. The proposed release
+ may be assigned
+ "Alpha", "Beta" or "General Availability" classifications
+ by majority vote.
+ Once a release is classified by the PMC Members, it may be
+ distributed to
+ the general public on behalf of the Foundation.
+ Distributions may be
+ reclassified or withdrawn by majority vote, but the
+ release number may not
+ be reused by another distribution.
+ </p>
+
+ </subsection>
+ </section>
+
+ <section>
+ <p class="right">
+ Next:
+ <a href="releases.html">Release Guidelines</a>
+ </p>
+ </section>
-</body>
+ </body>
</document>
Modified: struts/site/trunk/xdocs/download.xml
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/download.xml?rev=376838&r1=376837&r2=376838&view=diff
==============================================================================
--- struts/site/trunk/xdocs/download.xml (original)
+++ struts/site/trunk/xdocs/download.xml Fri Feb 10 12:58:33 2006
@@ -18,235 +18,350 @@
-->
<document>
-<properties>
- <title>Downloading</title>
-</properties>
-
-<body>
-
- <section name="Downloading Struts">
- <a name="downloading"/>
-
- <p>
- Use the links below to download Apache Struts from one of our mirrors.
- You <strong>must</strong> <a href="#verify">verify the integrity</a>
- of the downloaded files using signatures downloaded from our main
- distribution directory.
- </p>
-
- <subsection name="Mirror">
- <a name="mirror"/>
-
- <p>
- [if-any logo]
- <a href="[link]"><img align="right" src="[logo]" border="0" alt="logo" /></a>
- [end]
- The currently selected mirror is <b>[preferred]</b>.
- If you encounter a problem with this mirror,
- please select another mirror.
- If all mirrors are failing, there are <i>backup</i> mirrors
- (at the end of the mirrors list) that should be available.
- </p>
-
- <form action="[location]" method="get" id="SelectMirror">
- Other mirrors:
- <select name="Preferred">
- [if-any http]
- [for http]<option value="[http]">[http]</option>[end]
- [end]
- [if-any ftp]
- [for ftp]<option value="[ftp]">[ftp]</option>[end]
- [end]
- [if-any backup]
- [for backup]<option value="[backup]">[backup] (backup)</option>[end]
- [end]
- </select>
- <input type="submit" value="Change" />
- </form>
-
- <p>
- You may also consult the
- <a href="http://www.apache.org/mirrors/">complete list of mirrors</a>.
- </p>
+ <properties>
+ <title>Downloading</title>
+ </properties>
+
+ <body>
+
+ <section name="Downloading Struts">
+ <a name="downloading"/>
+
+ <p>
+ Use the links below to download Apache Struts from one of our
+ mirrors.
+ You
+ <strong>must</strong>
+ <a href="#verify">verify the integrity</a>
+ of the downloaded files using signatures downloaded from our
+ main
+ distribution directory.
+ </p>
+
+ <subsection name="Mirror">
+ <a name="mirror"/>
+
+ <p>
+ [if-any logo]
+ <a href="[link]">
+ <img align="right" src="[logo]" border="0"
+ alt="logo"/>
+ </a>
+ [end]
+ The currently selected mirror is
+ <b>[preferred]</b>
+ .
+ If you encounter a problem with this mirror,
+ please select another mirror.
+ If all mirrors are failing, there are
+ <i>backup</i>
+ mirrors
+ (at the end of the mirrors list) that should be available.
+ </p>
+
+ <form action="[location]" method="get" id="SelectMirror">
+ Other mirrors:
+ <select name="Preferred">
+ [if-any http]
+ [for http]
+ <option value="[http]">[http]</option>
+ [end]
+ [end]
+ [if-any ftp]
+ [for ftp]
+ <option value="[ftp]">[ftp]</option>
+ [end]
+ [end]
+ [if-any backup]
+ [for backup]
+ <option value="[backup]">[backup] (backup)</option>
+ [end]
+ [end]
+ </select>
+ <input type="submit" value="Change"/>
+ </form>
+
+ <p>
+ You may also consult the
+ <a href="http://www.apache.org/mirrors/">complete list of
+ mirrors</a>
+ .
+ </p>
- </subsection>
+ </subsection>
</section>
<section name="Full Releases">
- <a name="struts-ga"/>
+ <a name="struts-ga"/>
- <a name="struts128"/>
- <subsection name="Struts 1.2.8">
+ <a name="struts128"/>
+ <subsection name="Struts 1.2.8">
- <p>
- Struts 1.2.8 is the latest production release of Struts Classic.
- It is available in a binary distribution, a source distribution,
- and a minimal library distribution.
- </p>
-
- <ul>
-
- <li>Binaries:
- <ul>
- <li>
- <a href="[preferred]/struts/binaries/struts-1.2.8-bin.zip">struts-1.2.8-bin.zip</a>
- [<a href="http://www.apache.org/dist/struts/binaries/struts-1.2.8-bin.zip.asc">PGP</a>]
- [<a href="http://www.apache.org/dist/struts/binaries/struts-1.2.8-bin.zip.md5">MD5</a>]
- </li>
- <li>
- <a href="[preferred]/struts/binaries/struts-1.2.8-bin.tar.gz">struts-1.2.8-bin.tar.gz</a>
- [<a href="http://www.apache.org/dist/struts/binaries/struts-1.2.8-bin.tar.gz.asc">PGP</a>]
- [<a href="http://www.apache.org/dist/struts/binaries/struts-1.2.8-bin.tar.gz.md5">MD5</a>]
- </li>
- </ul>
- </li>
-
- <li>Source:
- <ul>
- <li>
- <a href="[preferred]/struts/source/struts-1.2.8-src.zip">struts-1.2.8-src.zip</a>
- [<a href="http://www.apache.org/dist/struts/source/struts-1.2.8-src.zip.asc">PGP</a>]
- [<a href="http://www.apache.org/dist/struts/source/struts-1.2.8-src.zip.md5">MD5</a>]
- </li>
- <li>
- <a href="[preferred]/struts/source/struts-1.2.8-src.tar.gz">struts-1.2.8-src.tar.gz</a>
- [<a href="http://www.apache.org/dist/struts/source/struts-1.2.8-src.tar.gz.asc">PGP</a>]
- [<a href="http://www.apache.org/dist/struts/source/struts-1.2.8-src.tar.gz.md5">MD5</a>]
- </li>
- </ul>
- </li>
-
- <li>Library:
- <ul>
- <li>
- <a href="[preferred]/struts/library/struts-1.2.8-lib.zip">struts-1.2.8-lib.zip</a>
- [<a href="http://www.apache.org/dist/struts/library/struts-1.2.8-lib.zip.asc">PGP</a>]
- [<a href="http://www.apache.org/dist/struts/library/struts-1.2.8-lib.zip.md5">MD5</a>]
- </li>
- <li>
- <a href="[preferred]/struts/library/struts-1.2.8-lib.tar.gz">struts-1.2.8-lib.tar.gz</a>
- [<a href="http://www.apache.org/dist/struts/library/struts-1.2.8-lib.tar.gz.asc">PGP</a>]
- [<a href="http://www.apache.org/dist/struts/library/struts-1.2.8-lib.tar.gz.md5">MD5</a>]
- </li>
- </ul>
- </li>
-
- </ul>
-
- </subsection>
-
- <a name="struts-scripting-101"/>
- <subsection name="Struts Scripting 1.0.1">
-
- <p>
- Struts Scripting 1.0.1 is the latest production release of Struts Scripting.
- It is available in a binary distribution and in a source distribution.
- </p>
-
- <ul>
-
- <li>Binaries:
- <ul>
- <li>
- <a href="[preferred]/struts/scripting/binaries/struts-scripting-1.0.1.zip">struts-scripting-1.0.1.zip</a>
- [<a href="http://www.apache.org/dist/struts/scripting/binaries/struts-scripting-1.0.1.zip.asc">PGP</a>]
- [<a href="http://www.apache.org/dist/struts/scripting/binaries/struts-scripting-1.0.1.zip.md5">MD5</a>]
- </li>
- <li>
- <a href="[preferred]/struts/scripting/binaries/struts-scripting-1.0.1.tar.gz">struts-scripting-1.0.1.tar.gz</a>
- [<a href="http://www.apache.org/dist/struts/scripting/binaries/struts-scripting-1.0.1.tar.gz.asc">PGP</a>]
- [<a href="http://www.apache.org/dist/struts/scripting/binaries/struts-scripting-1.0.1.tar.gz.md5">MD5</a>]
- </li>
- </ul>
- </li>
-
- <li>Source:
- <ul>
- <li>
- <a href="[preferred]/struts/scripting/source/struts-scripting-1.0.1-src.zip">struts-scripting-1.0.1-src.zip</a>
- [<a href="http://www.apache.org/dist/struts/scripting/source/struts-scripting-1.0.1-src.zip.asc">PGP</a>]
- [<a href="http://www.apache.org/dist/struts/scripting/source/struts-scripting-1.0.1-src.zip.md5">MD5</a>]
- </li>
- <li>
- <a href="[preferred]/struts/scripting/source/struts-scripting-1.0.1-src.tar.gz">struts-scripting-1.0.1-src.tar.gz</a>
- [<a href="http://www.apache.org/dist/struts/scripting/source/struts-scripting-1.0.1-src.tar.gz.asc">PGP</a>]
- [<a href="http://www.apache.org/dist/struts/scripting/source/struts-scripting-1.0.1-src.tar.gz.md5">MD5</a>]
- </li>
- </ul>
- </li>
- </ul>
-
- </subsection>
- <a name="strutsarchive"/>
- <subsection name="Older Versions">
-
- <p>
- Older versions of Struts Classic are available from the
- <a href="http://archive.apache.org/dist/struts/">Archive Site</a>.
- </p>
+ <p>
+ Struts 1.2.8 is the latest production release of Struts
+ Classic.
+ It is available in a binary distribution, a source
+ distribution,
+ and a minimal library distribution.
+ </p>
+
+ <ul>
+
+ <li>Binaries:
+ <ul>
+ <li>
+ <a href="[preferred]/struts/binaries/struts-1.2.8-bin.zip">
+ struts-1.2.8-bin.zip</a>
+ [
+ <a href="http://www.apache.org/dist/struts/binaries/struts-1.2.8-bin.zip.asc">
+ PGP</a>
+ ]
+ [
+ <a href="http://www.apache.org/dist/struts/binaries/struts-1.2.8-bin.zip.md5">
+ MD5</a>
+ ]
+ </li>
+ <li>
+ <a href="[preferred]/struts/binaries/struts-1.2.8-bin.tar.gz">
+ struts-1.2.8-bin.tar.gz</a>
+ [
+ <a href="http://www.apache.org/dist/struts/binaries/struts-1.2.8-bin.tar.gz.asc">
+ PGP</a>
+ ]
+ [
+ <a href="http://www.apache.org/dist/struts/binaries/struts-1.2.8-bin.tar.gz.md5">
+ MD5</a>
+ ]
+ </li>
+ </ul>
+ </li>
+
+ <li>Source:
+ <ul>
+ <li>
+ <a href="[preferred]/struts/source/struts-1.2.8-src.zip">
+ struts-1.2.8-src.zip</a>
+ [
+ <a href="http://www.apache.org/dist/struts/source/struts-1.2.8-src.zip.asc">
+ PGP</a>
+ ]
+ [
+ <a href="http://www.apache.org/dist/struts/source/struts-1.2.8-src.zip.md5">
+ MD5</a>
+ ]
+ </li>
+ <li>
+ <a href="[preferred]/struts/source/struts-1.2.8-src.tar.gz">
+ struts-1.2.8-src.tar.gz</a>
+ [
+ <a href="http://www.apache.org/dist/struts/source/struts-1.2.8-src.tar.gz.asc">
+ PGP</a>
+ ]
+ [
+ <a href="http://www.apache.org/dist/struts/source/struts-1.2.8-src.tar.gz.md5">
+ MD5</a>
+ ]
+ </li>
+ </ul>
+ </li>
+
+ <li>Library:
+ <ul>
+ <li>
+ <a href="[preferred]/struts/library/struts-1.2.8-lib.zip">
+ struts-1.2.8-lib.zip</a>
+ [
+ <a href="http://www.apache.org/dist/struts/library/struts-1.2.8-lib.zip.asc">
+ PGP</a>
+ ]
+ [
+ <a href="http://www.apache.org/dist/struts/library/struts-1.2.8-lib.zip.md5">
+ MD5</a>
+ ]
+ </li>
+ <li>
+ <a href="[preferred]/struts/library/struts-1.2.8-lib.tar.gz">
+ struts-1.2.8-lib.tar.gz</a>
+ [
+ <a href="http://www.apache.org/dist/struts/library/struts-1.2.8-lib.tar.gz.asc">
+ PGP</a>
+ ]
+ [
+ <a href="http://www.apache.org/dist/struts/library/struts-1.2.8-lib.tar.gz.md5">
+ MD5</a>
+ ]
+ </li>
+ </ul>
+ </li>
+
+ </ul>
+
+ </subsection>
+
+ <a name="struts-scripting-101"/>
+ <subsection name="Struts Scripting 1.0.1">
+
+ <p>
+ Struts Scripting 1.0.1 is the latest production release of
+ Struts Scripting.
+ It is available in a binary distribution and in a source
+ distribution.
+ </p>
+
+ <ul>
+
+ <li>Binaries:
+ <ul>
+ <li>
+ <a href="[preferred]/struts/scripting/binaries/struts-scripting-1.0.1.zip">
+ struts-scripting-1.0.1.zip</a>
+ [
+ <a href="http://www.apache.org/dist/struts/scripting/binaries/struts-scripting-1.0.1.zip.asc">
+ PGP</a>
+ ]
+ [
+ <a href="http://www.apache.org/dist/struts/scripting/binaries/struts-scripting-1.0.1.zip.md5">
+ MD5</a>
+ ]
+ </li>
+ <li>
+ <a href="[preferred]/struts/scripting/binaries/struts-scripting-1.0.1.tar.gz">
+ struts-scripting-1.0.1.tar.gz</a>
+ [
+ <a href="http://www.apache.org/dist/struts/scripting/binaries/struts-scripting-1.0.1.tar.gz.asc">
+ PGP</a>
+ ]
+ [
+ <a href="http://www.apache.org/dist/struts/scripting/binaries/struts-scripting-1.0.1.tar.gz.md5">
+ MD5</a>
+ ]
+ </li>
+ </ul>
+ </li>
+
+ <li>Source:
+ <ul>
+ <li>
+ <a href="[preferred]/struts/scripting/source/struts-scripting-1.0.1-src.zip">
+ struts-scripting-1.0.1-src.zip</a>
+ [
+ <a href="http://www.apache.org/dist/struts/scripting/source/struts-scripting-1.0.1-src.zip.asc">
+ PGP</a>
+ ]
+ [
+ <a href="http://www.apache.org/dist/struts/scripting/source/struts-scripting-1.0.1-src.zip.md5">
+ MD5</a>
+ ]
+ </li>
+ <li>
+ <a href="[preferred]/struts/scripting/source/struts-scripting-1.0.1-src.tar.gz">
+ struts-scripting-1.0.1-src.tar.gz</a>
+ [
+ <a href="http://www.apache.org/dist/struts/scripting/source/struts-scripting-1.0.1-src.tar.gz.asc">
+ PGP</a>
+ ]
+ [
+ <a href="http://www.apache.org/dist/struts/scripting/source/struts-scripting-1.0.1-src.tar.gz.md5">
+ MD5</a>
+ ]
+ </li>
+ </ul>
+ </li>
+ </ul>
+
+ </subsection>
+ <a name="strutsarchive"/>
+ <subsection name="Older Versions">
+
+ <p>
+ Older versions of Struts Classic are available from the
+ <a href="http://archive.apache.org/dist/struts/">Archive
+ Site</a>
+ .
+ </p>
- </subsection>
+ </subsection>
</section>
<section name="Beta Releases">
- <a name="struts-beta"/>
+ <a name="struts-beta"/>
- <p>
- None currently available.
- </p>
+ <p>
+ None currently available.
+ </p>
</section>
<section name="Verify the integrity of the files" href="verify">
- <p>
- It is essential that you verify the integrity of the
- downloaded files using the PGP or MD5 signatures.
- </p>
-
- <p>
- The PGP signatures can be verified using PGP or GPG.
- First download the
- <a href="http://www.apache.org/dist/struts/KEYS">KEYS</a>
- as well as the <code>asc</code> signature file for the particular
- distribution.
- Make sure you get these files from the
- <a href="http://www.apache.org/dist/struts/">main distribution
- directory</a>, rather than from a mirror.
- Then verify the signatures using
- </p>
-
- <p>
- <code>
- % pgpk -a KEYS<br />
- % pgpv ${filename}.tar.gz.asc<br />
- </code>
- <em>or</em><br />
- <code>
- % pgp -ka KEYS<br />
- % pgp ${filename}.tar.gz.asc<br />
- </code>
- <em>or</em><br />
- <code>
- % gpg --import KEYS<br />
- % gpg --verify ${filename}.tar.gz.asc
- </code>
- </p>
-
- <p>
- Alternatively, you can verify the MD5 signature on the files.
- A Unix program called <code>md5</code> or <code>md5sum</code> is
- included in many Unix distributions.
- It is also available as part of
- <a href="http://www.gnu.org/software/textutils/textutils.html">GNU
- Textutils</a>. Windows users can get binary md5 programs from
- <a href="http://www.fourmilab.ch/md5/">here</a>,
- <a href="http://www.pc-tools.net/win32/freeware/console/">here</a>, or
- <a href="http://www.slavasoft.com/fsum/">here</a>.
- </p>
+ <p>
+ It is essential that you verify the integrity of the
+ downloaded files using the PGP or MD5 signatures.
+ </p>
+
+ <p>
+ The PGP signatures can be verified using PGP or GPG.
+ First download the
+ <a href="http://www.apache.org/dist/struts/KEYS">KEYS</a>
+ as well as the
+ <code>asc</code>
+ signature file for the particular
+ distribution.
+ Make sure you get these files from the
+ <a href="http://www.apache.org/dist/struts/">main distribution
+ directory</a>
+ , rather than from a mirror.
+ Then verify the signatures using
+ </p>
+
+ <p>
+ <code>
+ % pgpk -a KEYS
+ <br/>
+ % pgpv ${filename}.tar.gz.asc
+ <br/>
+ </code>
+ <em>or</em>
+ <br/>
+ <code>
+ % pgp -ka KEYS
+ <br/>
+ % pgp ${filename}.tar.gz.asc
+ <br/>
+ </code>
+ <em>or</em>
+ <br/>
+ <code>
+ % gpg --import KEYS
+ <br/>
+ % gpg --verify ${filename}.tar.gz.asc
+ </code>
+ </p>
+
+ <p>
+ Alternatively, you can verify the MD5 signature on the files.
+ A Unix program called
+ <code>md5</code>
+ or
+ <code>md5sum</code>
+ is
+ included in many Unix distributions.
+ It is also available as part of
+ <a href="http://www.gnu.org/software/textutils/textutils.html">
+ GNU
+ Textutils</a>
+ . Windows users can get binary md5 programs from
+ <a href="http://www.fourmilab.ch/md5/">here</a>
+ ,
+ <a href="http://www.pc-tools.net/win32/freeware/console/">
+ here</a>
+ , or
+ <a href="http://www.slavasoft.com/fsum/">here</a>
+ .
+ </p>
</section>
-</body>
+ </body>
</document>
Modified: struts/site/trunk/xdocs/downloads.xml
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/downloads.xml?rev=376838&r1=376837&r2=376838&view=diff
==============================================================================
--- struts/site/trunk/xdocs/downloads.xml (original)
+++ struts/site/trunk/xdocs/downloads.xml Fri Feb 10 12:58:33 2006
@@ -18,241 +18,302 @@
-->
<document>
-<properties>
- <title>Acquiring</title>
-</properties>
-
-<body>
- <a name="Acquiring"/>
- <section name="Acquiring Apache Struts products">
-
- <p>
- Apache Struts products are made available to the public at no charge
- in both binary and source distributions under the
- <a href="http://apache.org/licenses/">Apache Software License</a>.
- Each subproject offers a production release, as well as a milestone
- releases and "nightly" development builds.
- Individual JARs are also made available through
- <a href="http://maven.apache.org">Apache Maven</a> repositories,
- like <a href="http://ibiblio.org">ibiblio</a>.
- </p>
-
-<subsection name="Releases and Milestone Builds">
-<a name="ReleasesAndMilestones"/>
- <p>
- Releases and milestone builds of Struts products are available from
- the main Apache Struts distribution site, or from mirror sites.
- </p>
- <ul>
- <li>
- <strong>General Availability (GA) Releases</strong>
- <ul>
- <li>
- <a href="http://struts.apache.org/download.cgi">
- Struts 1.2.8
- </a>
- </li>
- <li>
- <a href="http://struts.apache.org/download.cgi">
- Struts Scripting 1.0.1
- </a>
- </li>
- </ul>
- </li>
- <li>
- <strong>Older Releases</strong> are available from the
- <ul>
- <li>
- <a href="http://archive.apache.org/dist/struts/">
- Archive Site
- </a>
- </li>
- </ul>
- </li>
- </ul>
-</subsection>
-
-<a name="DevelopmentBuilds"/>
-<subsection name="Development Builds">
-
- <p>
- The latest <em>development build</em> of Struts products are available
- <a href="http://svn.apache.org/dist/struts/">here</a>
- in binary, source and library distributions.
- Library distributions include any external depdencies
- needed to use a product with your application.
- </p>
-
- <p>
- Development builds are being reviewed for quality
- by the Apache Struts community.
- When a build is judged "ready for prime time",
- it is promoted to "General Availability" status and may be made
- the "Best Available" release.
- If the community feel that a build requires more testing,
- then it may be marked with "Beta" status.
- </p>
-
-</subsection>
-
-<a name="NightlyBuilds"/>
-<subsection name="Nightly Builds">
-
- <p>
- For developers who are helping to create and maintain Struts products,
- or who just want "the latest bits",
- the latest development version is made available each morning.
- Use at your own risk!
- </p>
-
- <p>
- Apache Struts development builds are managed using
- <a href="http://maven.apache.org/">Apache Maven</a>.
- Maven acquires the various JARs needed by Struts products
- and automaticaly shares JARs between Struts subprojects and other
- Maven projects.
- </p>
-
- <ul>
-
- <li>
- <a href="http://svn.apache.org/builds/struts/maven/">Nightly Builds</a>.
- </li>
-
- </ul>
-
- <p>
- Be sure to check the Release Notes for a nightly build,
- so you have a better idea of what you are getting!
- </p>
-
-</subsection>
-
-<a name="SourceCode"/>
-<subsection name="Source Code">
-
- <p>
- Access to the Apache Struts source repository is available through
- both
- <a href="http://svn.apache.org/viewcvs.cgi/struts/action/trunk/?root=Apache-SVN">
- web browser</a> and
- <a href="http://subversion.tigris.org/">
- Subversion client</a> interfaces.
- </p>
-
- <p>
- To download the trunk (HEAD revision) of any Struts subproject,
- a convenience directory has been added, named <b>current</b>.
- The current directory uses a Subversion feature called externals
- which stores properties on the directory.
- With those properties,
- Subversion has all the information it needs to automaticaly download
- the head revision of all the Struts subprojects.
- </p>
-
- <p>
- With the <a href="http://subversion.tigris.org/"> Subversion client</a>
- installed, obtaining a working copy of the Struts codebase is as simple as
- </p>
-
- <code>> svn checkout http://svn.apache.org/repos/asf/struts/current</code>
-
- <p>
- While Externals work well in practice, there are caveats.
- For example,
- since all the subdirectories are still really different slices
- from the repository,
- relative paths might not work the way you expect.
- For more, see the
- <a href="http://svnbook.red-bean.com/en/1.1/ch07s04.html">Externals
- Definitions</a> section of the
- <a href="http://svnbook.red-bean.com/">Subversion Book</a>.
- </p>
-
-
- <p>
- To check out individual sub-projects from the Subversion repository,
- you can specify one of the following URLs:
- </p>
-
- <ul>
- <li>http://svn.apache.org/repos/asf/struts/action/trunk</li>
- <li>http://svn.apache.org/repos/asf/struts/apps/trunk</li>
- <li>http://svn.apache.org/repos/asf/struts/el/trunk</li>
- <li>http://svn.apache.org/repos/asf/struts/faces/trunk</li>
- <li>http://svn.apache.org/repos/asf/struts/flow/trunk</li>
- <li>http://svn.apache.org/repos/asf/struts/sandbox/trunk</li>
- <li>http://svn.apache.org/repos/asf/struts/scripting/trunk</li>
- <li>http://svn.apache.org/repos/asf/struts/shale/trunk</li>
- <li>http://svn.apache.org/repos/asf/struts/taglib/trunk</li>
- <li>http://svn.apache.org/repos/asf/struts/tiles/trunk</li>
- </ul>
-
- <p>
- (Committers with write access should use the <strong>https</strong> protocol instead.
- See the ASF <a href="http://www.apache.org/dev/version-control.html#https-svn">
- Source Code Repositories</a> page for details.)
- </p>
-
- <p>
- <strong>Warning:</strong>
- If you try to check out everything under 'struts',
- be aware that you will get not just the most recent code ('trunk'),
- but a copy of every tag and branch ever created
- for Struts.
- A complete checkout of Struts from day one, including all the branches,
- will take some time and might max out your disk volume!
- </p>
-
- <p>
- For more about using version control systems at Apache,
- see the ASF's <a href="http://www.apache.org/dev/version-control.html#anon-svn">
- Source Code Repositories</a> page.
- For more about how Apache Struts uses Subversion, see our
- <a href="http://wiki.apache.org/struts/StrutsMaintenanceSvn">
- Subversion wiki page</a>.
- </p>
-
-</subsection>
-
-<a name="Building"/>
-<subsection name="Building Struts">
-
- <p>
- If you are building a Struts subproject from source,
- we recommend that you install and use <a href="http://maven.apache.org">
- Apache Maven</a> 1.0.2,
- since Maven will acquire whatever external JARs your system may need.
- Of course,
- you can still use your build system of choice to build your own
- applications!
- </p>
-
- <p>
- With Maven installed, building the entire Struts codebase is as simple as
- </p>
-
- <code>/current/build/> maven build-all</code>
-
- <p>
- Maven will automatically download any dependencies as needed.
- </p>
-
- <p>
- For more about using Maven to build Apache Struts,
- see our <a href="http://wiki.apache.org/struts/StrutsMaintenanceMaven">
- Maven wiki page</a>.
- </p>
-
-</subsection>
-
-</section>
-
-<section>
- <p class="right">
- Next: <a href="bylaws.html">PMC Bylaws</a>
- </p>
-</section>
+ <properties>
+ <title>Acquiring</title>
+ </properties>
+
+ <body>
+ <a name="Acquiring"/>
+ <section name="Acquiring Apache Struts products">
+
+ <p>
+ Apache Struts products are made available to the public at no
+ charge
+ in both binary and source distributions under the
+ <a href="http://apache.org/licenses/">Apache Software
+ License</a>
+ .
+ Each subproject offers a production release, as well as a
+ milestone
+ releases and "nightly" development builds.
+ Individual JARs are also made available through
+ <a href="http://maven.apache.org">Apache Maven</a>
+ repositories,
+ like
+ <a href="http://ibiblio.org">ibiblio</a>
+ .
+ </p>
+
+ <subsection name="Releases and Milestone Builds">
+ <a name="ReleasesAndMilestones"/>
+ <p>
+ Releases and milestone builds of Struts products are
+ available from
+ the main Apache Struts distribution site, or from mirror
+ sites.
+ </p>
+ <ul>
+ <li>
+ <strong>General Availability (GA) Releases</strong>
+ <ul>
+ <li>
+ <a href="http://struts.apache.org/download.cgi">
+ Struts 1.2.8
+ </a>
+ </li>
+ <li>
+ <a href="http://struts.apache.org/download.cgi">
+ Struts Scripting 1.0.1
+ </a>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <strong>Older Releases</strong>
+ are available from the
+ <ul>
+ <li>
+ <a href="http://archive.apache.org/dist/struts/">
+ Archive Site
+ </a>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </subsection>
+
+ <a name="DevelopmentBuilds"/>
+ <subsection name="Development Builds">
+
+ <p>
+ The latest
+ <em>development build</em>
+ of Struts products are available
+ <a href="http://svn.apache.org/dist/struts/">here</a>
+ in binary, source and library distributions.
+ Library distributions include any external depdencies
+ needed to use a product with your application.
+ </p>
+
+ <p>
+ Development builds are being reviewed for quality
+ by the Apache Struts community.
+ When a build is judged "ready for prime time",
+ it is promoted to "General Availability" status and may be
+ made
+ the "Best Available" release.
+ If the community feel that a build requires more testing,
+ then it may be marked with "Beta" status.
+ </p>
+
+ </subsection>
+
+ <a name="NightlyBuilds"/>
+ <subsection name="Nightly Builds">
+
+ <p>
+ For developers who are helping to create and maintain
+ Struts products,
+ or who just want "the latest bits",
+ the latest development version is made available each
+ morning.
+ Use at your own risk!
+ </p>
+
+ <p>
+ Apache Struts development builds are managed using
+ <a href="http://maven.apache.org/">Apache Maven</a>
+ .
+ Maven acquires the various JARs needed by Struts products
+ and automaticaly shares JARs between Struts subprojects
+ and other
+ Maven projects.
+ </p>
+
+ <ul>
+
+ <li>
+ <a href="http://svn.apache.org/builds/struts/maven/">
+ Nightly Builds</a>
+ .
+ </li>
+
+ </ul>
+
+ <p>
+ Be sure to check the Release Notes for a nightly build,
+ so you have a better idea of what you are getting!
+ </p>
+
+ </subsection>
+
+ <a name="SourceCode"/>
+ <subsection name="Source Code">
+
+ <p>
+ Access to the Apache Struts source repository is available
+ through
+ both
+ <a href="http://svn.apache.org/viewcvs.cgi/struts/action/trunk/?root=Apache-SVN">
+ web browser</a>
+ and
+ <a href="http://subversion.tigris.org/">
+ Subversion client</a>
+ interfaces.
+ </p>
+
+ <p>
+ To download the trunk (HEAD revision) of any Struts
+ subproject,
+ a convenience directory has been added, named
+ <b>current</b>
+ .
+ The current directory uses a Subversion feature called
+ externals
+ which stores properties on the directory.
+ With those properties,
+ Subversion has all the information it needs to
+ automaticaly download
+ the head revision of all the Struts subprojects.
+ </p>
+
+ <p>
+ With the
+ <a href="http://subversion.tigris.org/">Subversion
+ client</a>
+ installed, obtaining a working copy of the Struts codebase
+ is as simple as
+ </p>
+
+ <code>> svn checkout
+ http://svn.apache.org/repos/asf/struts/current</code>
+
+ <p>
+ While Externals work well in practice, there are caveats.
+ For example,
+ since all the subdirectories are still really different
+ slices
+ from the repository,
+ relative paths might not work the way you expect.
+ For more, see the
+ <a href="http://svnbook.red-bean.com/en/1.1/ch07s04.html">
+ Externals
+ Definitions</a>
+ section of the
+ <a href="http://svnbook.red-bean.com/">Subversion Book</a>
+ .
+ </p>
+
+
+ <p>
+ To check out individual sub-projects from the Subversion
+ repository,
+ you can specify one of the following URLs:
+ </p>
+
+ <ul>
+ <li>
+ http://svn.apache.org/repos/asf/struts/action/trunk</li>
+ <li>http://svn.apache.org/repos/asf/struts/apps/trunk</li>
+ <li>http://svn.apache.org/repos/asf/struts/el/trunk</li>
+ <li>
+ http://svn.apache.org/repos/asf/struts/faces/trunk</li>
+ <li>http://svn.apache.org/repos/asf/struts/flow/trunk</li>
+ <li>
+ http://svn.apache.org/repos/asf/struts/sandbox/trunk</li>
+ <li>
+ http://svn.apache.org/repos/asf/struts/scripting/trunk</li>
+ <li>
+ http://svn.apache.org/repos/asf/struts/shale/trunk</li>
+ <li>
+ http://svn.apache.org/repos/asf/struts/taglib/trunk</li>
+ <li>
+ http://svn.apache.org/repos/asf/struts/tiles/trunk</li>
+ </ul>
+
+ <p>
+ (Committers with write access should use the
+ <strong>https</strong>
+ protocol instead.
+ See the ASF
+ <a href="http://www.apache.org/dev/version-control.html#https-svn">
+ Source Code Repositories</a>
+ page for details.)
+ </p>
+
+ <p>
+ <strong>Warning:</strong>
+ If you try to check out everything under 'struts',
+ be aware that you will get not just the most recent code
+ ('trunk'),
+ but a copy of every tag and branch ever created
+ for Struts.
+ A complete checkout of Struts from day one, including all
+ the branches,
+ will take some time and might max out your disk volume!
+ </p>
+
+ <p>
+ For more about using version control systems at Apache,
+ see the ASF's
+ <a href="http://www.apache.org/dev/version-control.html#anon-svn">
+ Source Code Repositories</a>
+ page.
+ For more about how Apache Struts uses Subversion, see our
+ <a href="http://wiki.apache.org/struts/StrutsMaintenanceSvn">
+ Subversion wiki page</a>
+ .
+ </p>
+
+ </subsection>
+
+ <a name="Building"/>
+ <subsection name="Building Struts">
+
+ <p>
+ If you are building a Struts subproject from source,
+ we recommend that you install and use
+ <a href="http://maven.apache.org">
+ Apache Maven</a>
+ 1.0.2,
+ since Maven will acquire whatever external JARs your
+ system may need.
+ Of course,
+ you can still use your build system of choice to build
+ your own
+ applications!
+ </p>
+
+ <p>
+ With Maven installed, building the entire Struts codebase
+ is as simple as
+ </p>
+
+ <code>/current/build/> maven build-all</code>
+
+ <p>
+ Maven will automatically download any dependencies as
+ needed.
+ </p>
+
+ <p>
+ For more about using Maven to build Apache Struts,
+ see our
+ <a href="http://wiki.apache.org/struts/StrutsMaintenanceMaven">
+ Maven wiki page</a>
+ .
+ </p>
+
+ </subsection>
+
+ </section>
+
+ <section>
+ <p class="right">
+ Next:
+ <a href="bylaws.html">PMC Bylaws</a>
+ </p>
+ </section>
-</body>
+ </body>
</document>
Modified: struts/site/trunk/xdocs/faqs.xml
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/faqs.xml?rev=376838&r1=376837&r2=376838&view=diff
==============================================================================
--- struts/site/trunk/xdocs/faqs.xml (original)
+++ struts/site/trunk/xdocs/faqs.xml Fri Feb 10 12:58:33 2006
@@ -18,33 +18,36 @@
-->
<document>
-<properties>
- <title>FAQs</title>
-</properties>
+ <properties>
+ <title>FAQs</title>
+ </properties>
-<body>
+ <body>
-<section name="FAQs">
+ <section name="FAQs">
- <ul>
+ <ul>
- <li>
- <a href="kickstart.html">Kickstart FAQ</a> (read me first)
- </li>
+ <li>
+ <a href="kickstart.html">Kickstart FAQ</a>
+ (read me first)
+ </li>
- <li>
- <a href="helping.html">How to Help FAQ</a>
- </li>
+ <li>
+ <a href="helping.html">How to Help FAQ</a>
+ </li>
- </ul>
+ </ul>
-</section>
+ </section>
- <section>
- <p class="right">
- <strong>Next:</strong> <a href="kickstart.html">Kickstart FAQ</a>
- </p>
- </section>
+ <section>
+ <p class="right">
+ <strong>Next:</strong>
+ <a href="kickstart.html">Kickstart FAQ</a>
+ </p>
+ </section>
-</body></document>
+ </body>
+</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org