Project Management Committee Charter

Delivered-To: mailing list dev@struts.apache.org Received: (qmail 14984 invoked by uid 500); 10 Feb 2006 20:59:09 -0000 Received: (qmail 14973 invoked by uid 99); 10 Feb 2006 20:59:09 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2006 12:59:09 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 10 Feb 2006 12:59:01 -0800 Received: (qmail 66696 invoked by uid 65534); 10 Feb 2006 20:58:41 -0000 Message-ID: <20060210205841.66694.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: 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 Date: Fri, 10 Feb 2006 20:58:36 -0000 To: commits@struts.apache.org From: husted@apache.org X-Mailer: svnmailer-1.0.6 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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 @@ --> - - Project Management Committee Charter - - - - -

- -

- Struts is a Project of the - Apache Software Foundation (ASF), formed by a resolution of the - ASF Board of - Directors. As an ASF Project, Struts is subject to the - ASF Bylaws - and the direction of the ASF Board. -

- - - -

- 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. -

- -

- Users. - 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. -

- -

- Contributors. - 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. -

- -

- Committers. - Contributors who give frequent and valuable contributions to a - subproject of the Project can have their status promoted to that of - a "Committer" 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. -

- -

- Project Management Committee (PMC). - Committers and other volunteers who frequently participate with - valuable contributions may have their status promoted to that of a - "Project Management Committee Member". The PMC - is responsible for the day-to-day management of the Project. -

- - - - - -

- 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 - Volunteers page. -

- - - - - -

- 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 - Apache Software License. All releases of a Struts subproject - must be sanctioned by the Project Management Committee. -

- - - - - -

- 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". -

- -

- 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. -

- -

- 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. -

- - - - - -

- All Volunteers are encouraged to participate in decisions, but the - decision itself is made by the Project Management Committee. - The Project is a "Minimum Threshold Meritocracy". -

- - - - - -

- 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. -

- -

- The act of voting carries certain obligations. Voters are not only - stating their opinion, they are also agreeing to help do the work. -

- -

Each vote can be made in one of three flavors:

- - - - - - - - - - - - - - - - - -

- "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). -

+/-0

- "Abstain," "no opinion". An abstention may - have detrimental effects if too many people abstain. -

-1

- "No." On issues where consensus is required, this vote - counts as a veto. 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. -

- 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. -

- -

- An action requiring consensus approval must receive at least - 3 binding +1 votes and no binding - vetos. An action requiring majority approval must receive - at least 3 binding +1 votes and more - +1 votes than -1 votes. All other - action items are considered to have lazy approval until somebody - votes -1, after which point they are decided by - either consensus or majority vote, depending on the type of action - item. -

- 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. -

- - - - -

- All decisions revolve around "Action - Items." Action Items consist of the following: -

- -

Long Term Plans
Short Term Plans
Product Changes
Showstoppers
Release Plan
Release Grade

- - - - - -

- 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. -

- - - - - -

- 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. -

- - - - - -

- All product changes to the repository are subject to - lazy consensus. -

- - - - - -

- 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. -

- - - - - -

- 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. -

- - - - - -

- 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. -

- - -

- -

- Next: Release Guidelines -

+ + Project Management Committee Charter + + + + +

+ +

+ Struts is a Project of the + + Apache Software Foundation + (ASF), formed by a resolution of the + ASF Board of + Directors + . As an ASF Project, Struts is subject to the + ASF + Bylaws + and the direction of the ASF Board. +

+ + + +

+ 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. +

+ +

+ Users. + 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. +

+ +

+ Contributors. + 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. +

+ +

+ Committers. + Contributors who give frequent and valuable contributions + to a + subproject of the Project can have their status promoted + to that of + a " + Committer + " 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. +

+ +

+ Project Management Committee (PMC). + Committers and other volunteers who frequently participate + with + valuable contributions may have their status promoted to + that of a + " + Project Management Committee Member + ". The PMC + is responsible for the day-to-day management of the + Project. +

+ + + + + +

+ 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 + Volunteers page + . +

+ + + + + +

+ 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 + + Apache Software License + . All releases of a Struts subproject + must be sanctioned by the Project Management Committee. +

+ + + + + +

+ 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". +

+ +

+ 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. +

+ +

+ 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. +

+ + + + + +

+ All Volunteers are encouraged to participate in decisions, + but the + decision itself is made by the Project Management + Committee. + The Project is a " + Minimum Threshold Meritocracy + ". +

+ + + + + +

+ 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. +

+ +

+ The act of voting carries certain obligations. Voters are + not only + stating their opinion, they are also agreeing to help do + the work. +

+ +

Each vote can be made in one of three flavors:

+ + + + + + + + + + + + + + + + + +

+ +1 +

+ "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). +

+ +/-0 +

+ "Abstain," "no opinion". An + abstention may + have detrimental effects if too many people + abstain. +

+ -1 +

+ "No." On issues where consensus is + required, this vote + counts as a + veto + . 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. +

+ 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. +

+ +

+ An action requiring consensus approval must receive at + least + 3 binding +1 + votes and + no binding + vetos + . An action requiring majority approval must receive + at least + 3 binding +1 + votes and more + +1 + votes than + -1 + votes. All other + action items are considered to have lazy approval until + somebody + votes + -1 + , after which point they are decided by + either consensus or majority vote, depending on the type + of action + item. +

+ 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. +

+ + + + +

+ All decisions revolve around " + Action + Items. + " Action Items consist of the following: +

+ +

Long Term Plans
Short Term Plans
Product Changes
Showstoppers
Release Plan
Release Grade

+ + + + + +

+ 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. +

+ + + + + +

+ 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. +

+ + + + + +

+ All product changes to the repository are subject to + lazy consensus. +

+ + + + + +

+ 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. +

+ + + + + +

+ 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. +

+ + + + + +

+ 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. +

+ + +

+ +

+ Next: + Release Guidelines +

- + 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 @@ --> - - Downloading - - - - -

- - -

- Use the links below to download Apache Struts from one of our mirrors. - You must verify the integrity - of the downloaded files using signatures downloaded from our main - distribution directory. -

- - - - -

- [if-any logo] - - [end] - The currently selected mirror is [preferred]. - If you encounter a problem with this mirror, - please select another mirror. - If all mirrors are failing, there are backup mirrors - (at the end of the mirrors list) that should be available. -

- - - -

- You may also consult the - complete list of mirrors. -

+ + Downloading + + + + +

+ + +

+ Use the links below to download Apache Struts from one of our + mirrors. + You + must + verify the integrity + of the downloaded files using signatures downloaded from our + main + distribution directory. +

+ + + + +

+ [if-any logo] + + + + [end] + The currently selected mirror is + [preferred] + . + If you encounter a problem with this mirror, + please select another mirror. + If all mirrors are failing, there are + backup + mirrors + (at the end of the mirrors list) that should be available. +

+ + + +

+ You may also consult the + complete list of + mirrors + . +

- +

- + - - + + -

- 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. -

- -

Binaries: -
- - struts-1.2.8-bin.zip - [PGP] - [MD5] -
- - struts-1.2.8-bin.tar.gz - [PGP] - [MD5] -
-
Source: -
- - struts-1.2.8-src.zip - [PGP] - [MD5] -
- - struts-1.2.8-src.tar.gz - [PGP] - [MD5] -
-
Library: -
- - struts-1.2.8-lib.zip - [PGP] - [MD5] -
- - struts-1.2.8-lib.tar.gz - [PGP] - [MD5] -
-

- - - - - - -

- 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. -

- -

Binaries: -
- - struts-scripting-1.0.1.zip - [PGP] - [MD5] -
- - struts-scripting-1.0.1.tar.gz - [PGP] - [MD5] -
-
Source: -
- - struts-scripting-1.0.1-src.zip - [PGP] - [MD5] -
- - struts-scripting-1.0.1-src.tar.gz - [PGP] - [MD5] -
-

- - - - - -

- Older versions of Struts Classic are available from the - Archive Site. -

+ 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. +

+ +

Binaries: +
- + + struts-1.2.8-bin.zip + [ + + PGP + ] + [ + + MD5 + ] +
- + + struts-1.2.8-bin.tar.gz + [ + + PGP + ] + [ + + MD5 + ] +
+
Source: +
- + + struts-1.2.8-src.zip + [ + + PGP + ] + [ + + MD5 + ] +
- + + struts-1.2.8-src.tar.gz + [ + + PGP + ] + [ + + MD5 + ] +
+
Library: +
- + + struts-1.2.8-lib.zip + [ + + PGP + ] + [ + + MD5 + ] +
- + + struts-1.2.8-lib.tar.gz + [ + + PGP + ] + [ + + MD5 + ] +
+

+ + + + + + +

+ 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. +

+ +

Binaries: +
- + + struts-scripting-1.0.1.zip + [ + + PGP + ] + [ + + MD5 + ] +
- + + struts-scripting-1.0.1.tar.gz + [ + + PGP + ] + [ + + MD5 + ] +
+
Source: +
- + + struts-scripting-1.0.1-src.zip + [ + + PGP + ] + [ + + MD5 + ] +
- + + struts-scripting-1.0.1-src.tar.gz + [ + + PGP + ] + [ + + MD5 + ] +
+

+ + + + + +

+ Older versions of Struts Classic are available from the + Archive + Site + . +

- +

- + -

- None currently available. -

+ None currently available. +

- It is essential that you verify the integrity of the - downloaded files using the PGP or MD5 signatures. -

- -

- The PGP signatures can be verified using PGP or GPG. - First download the - KEYS - as well as the asc signature file for the particular - distribution. - Make sure you get these files from the - main distribution - directory, rather than from a mirror. - Then verify the signatures using -

- -

- - % pgpk -a KEYS - % pgpv ${filename}.tar.gz.asc - - or
- - % pgp -ka KEYS - % pgp ${filename}.tar.gz.asc - - or
- - % gpg --import KEYS - % gpg --verify ${filename}.tar.gz.asc - -

- -

- Alternatively, you can verify the MD5 signature on the files. - A Unix program called md5 or md5sum is - included in many Unix distributions. - It is also available as part of - GNU - Textutils. Windows users can get binary md5 programs from - here, - here, or - here. -

+ It is essential that you verify the integrity of the + downloaded files using the PGP or MD5 signatures. +

+ +

+ The PGP signatures can be verified using PGP or GPG. + First download the + KEYS + as well as the + asc + signature file for the particular + distribution. + Make sure you get these files from the + main distribution + directory + , rather than from a mirror. + Then verify the signatures using +

+ +

+ + % pgpk -a KEYS + + % pgpv ${filename}.tar.gz.asc + + + or +
+ + % pgp -ka KEYS + + % pgp ${filename}.tar.gz.asc + + + or +
+ + % gpg --import KEYS + + % gpg --verify ${filename}.tar.gz.asc + +

+ +

+ Alternatively, you can verify the MD5 signature on the files. + A Unix program called + md5 + or + md5sum + is + included in many Unix distributions. + It is also available as part of + + GNU + Textutils + . Windows users can get binary md5 programs from + here + , + + here + , or + here + . +

- + 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 @@ --> - - Acquiring - - - - -

- -

- Apache Struts products are made available to the public at no charge - in both binary and source distributions under the - Apache Software License. - Each subproject offers a production release, as well as a milestone - releases and "nightly" development builds. - Individual JARs are also made available through - Apache Maven repositories, - like ibiblio. -

- - - -

- Releases and milestone builds of Struts products are available from - the main Apache Struts distribution site, or from mirror sites. -

- General Availability (GA) Releases -
-
- - Struts 1.2.8 - -
-
- - Struts Scripting 1.0.1 - -
-
-
- Older Releases are available from the -
- - - Archive Site - -
-

- - - - - -

- The latest development build of Struts products are available - here - in binary, source and library distributions. - Library distributions include any external depdencies - needed to use a product with your application. -

- -

- 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. -

- - - - - - -

- 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! -

- -

- Apache Struts development builds are managed using - Apache Maven. - Maven acquires the various JARs needed by Struts products - and automaticaly shares JARs between Struts subprojects and other - Maven projects. -

- -

- Nightly Builds. -

- -

- Be sure to check the Release Notes for a nightly build, - so you have a better idea of what you are getting! -

- - - - - - -

- Access to the Apache Struts source repository is available through - both - - web browser and - - Subversion client interfaces. -

- -

- To download the trunk (HEAD revision) of any Struts subproject, - a convenience directory has been added, named current. - 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. -

- -

- With the Subversion client - installed, obtaining a working copy of the Struts codebase is as simple as -

- - > svn checkout http://svn.apache.org/repos/asf/struts/current - -

- 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 - Externals - Definitions section of the - Subversion Book. -

- - -

- To check out individual sub-projects from the Subversion repository, - you can specify one of the following URLs: -

- -

http://svn.apache.org/repos/asf/struts/action/trunk
http://svn.apache.org/repos/asf/struts/apps/trunk
http://svn.apache.org/repos/asf/struts/el/trunk
http://svn.apache.org/repos/asf/struts/faces/trunk
http://svn.apache.org/repos/asf/struts/flow/trunk
http://svn.apache.org/repos/asf/struts/sandbox/trunk
http://svn.apache.org/repos/asf/struts/scripting/trunk
http://svn.apache.org/repos/asf/struts/shale/trunk
http://svn.apache.org/repos/asf/struts/taglib/trunk
http://svn.apache.org/repos/asf/struts/tiles/trunk

- -

- (Committers with write access should use the https protocol instead. - See the ASF - Source Code Repositories page for details.) -

- -

- Warning: - 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! -

- -

- For more about using version control systems at Apache, - see the ASF's - Source Code Repositories page. - For more about how Apache Struts uses Subversion, see our - - Subversion wiki page. -

- - - - - - -

- If you are building a Struts subproject from source, - we recommend that you install and use - Apache Maven 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! -

- -

- With Maven installed, building the entire Struts codebase is as simple as -

- - /current/build/> maven build-all - -

- Maven will automatically download any dependencies as needed. -

- -

- For more about using Maven to build Apache Struts, - see our - Maven wiki page. -

- - - -

- -

- Next: PMC Bylaws -

+ + Acquiring + + + + +

+ +

+ Apache Struts products are made available to the public at no + charge + in both binary and source distributions under the + Apache Software + License + . + Each subproject offers a production release, as well as a + milestone + releases and "nightly" development builds. + Individual JARs are also made available through + Apache Maven + repositories, + like + ibiblio + . +

+ + + +

+ Releases and milestone builds of Struts products are + available from + the main Apache Struts distribution site, or from mirror + sites. +

+ General Availability (GA) Releases +
+
+ + Struts 1.2.8 + +
+
+ + Struts Scripting 1.0.1 + +
+
+
+ Older Releases + are available from the +
- + + Archive Site + +
+

+ + + + + +

+ The latest + development build + of Struts products are available + here + in binary, source and library distributions. + Library distributions include any external depdencies + needed to use a product with your application. +

+ +

+ 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. +

+ + + + + + +

+ 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! +

+ +

+ Apache Struts development builds are managed using + Apache Maven + . + Maven acquires the various JARs needed by Struts products + and automaticaly shares JARs between Struts subprojects + and other + Maven projects. +

+ +

+ + Nightly Builds + . +

+ +

+ Be sure to check the Release Notes for a nightly build, + so you have a better idea of what you are getting! +

+ + + + + + +

+ Access to the Apache Struts source repository is available + through + both + + web browser + and + + Subversion client + interfaces. +

+ +

+ To download the trunk (HEAD revision) of any Struts + subproject, + a convenience directory has been added, named + current + . + 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. +

+ +

+ With the + Subversion + client + installed, obtaining a working copy of the Struts codebase + is as simple as +

+ +

> svn checkout
+                    http://svn.apache.org/repos/asf/struts/current

+ +

+ 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 + + Externals + Definitions + section of the + Subversion Book + . +

+ + +

+ To check out individual sub-projects from the Subversion + repository, + you can specify one of the following URLs: +

+ +

+ http://svn.apache.org/repos/asf/struts/action/trunk
http://svn.apache.org/repos/asf/struts/apps/trunk
http://svn.apache.org/repos/asf/struts/el/trunk
+ http://svn.apache.org/repos/asf/struts/faces/trunk
http://svn.apache.org/repos/asf/struts/flow/trunk
+ http://svn.apache.org/repos/asf/struts/sandbox/trunk
+ http://svn.apache.org/repos/asf/struts/scripting/trunk
+ http://svn.apache.org/repos/asf/struts/shale/trunk
+ http://svn.apache.org/repos/asf/struts/taglib/trunk
+ http://svn.apache.org/repos/asf/struts/tiles/trunk

+ +

+ (Committers with write access should use the + https + protocol instead. + See the ASF + + Source Code Repositories + page for details.) +

+ +

+ Warning: + 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! +

+ +

+ For more about using version control systems at Apache, + see the ASF's + + Source Code Repositories + page. + For more about how Apache Struts uses Subversion, see our + + Subversion wiki page + . +

+ + + + + + +

+ If you are building a Struts subproject from source, + we recommend that you install and use + + Apache Maven + 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! +

+ +

+ With Maven installed, building the entire Struts codebase + is as simple as +

+ + /current/build/> maven build-all + +

+ Maven will automatically download any dependencies as + needed. +

+ +

+ For more about using Maven to build Apache Struts, + see our + + Maven wiki page + . +

+ + + +

+ +

+ Next: + PMC Bylaws +

- + 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 @@ --> - - FAQs - + + FAQs + - + -

- Kickstart FAQ (read me first) -
+ Kickstart FAQ + (read me first) +
- How to Help FAQ -
+ How to Help FAQ +

- Next: Kickstart FAQ -

+ Next: + Kickstart FAQ +

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