You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bval.apache.org by mb...@apache.org on 2012/03/09 21:14:18 UTC
svn commit: r1299018 [3/5] - in /bval/cms-site: ./ cgi-bin/ content/
content/board-reports/ content/coding/ content/images/ content/resources/
lib/ templates/
Added: bval/cms-site/content/images/Fotolia_License.txt
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/Fotolia_License.txt?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/images/Fotolia_License.txt (added)
+++ bval/cms-site/content/images/Fotolia_License.txt Fri Mar 9 20:14:15 2012
@@ -0,0 +1,119 @@
+The images whoose filenames begin with "Fotolia" have the following license
+and notice info -
+
+© Colorsky - Fotolia.com
+<a href="http://en.fotolia.com/id/10291515" title="" alt="">Colorsky</a> - Fotolia.com
+
+ROYALTY FREE FILES
+All the files offered on Fotolia are royalty free, it means they can be used:
+
+Without time limit
+Without diffusion number limit
+Without geographical limit
+
+MEDIA AND USES
+Files offered on Fotolia can be used on all kinds of media:
+
+WEB
+websites, blogs illustration
+Creation of newsletters, banners, icons...
+Creation of all kinds of professional digital documents (ex : slideshow)
+Creation of templates (websites or others) intended for resale (extended licenses)
+
+PRINT
+Creation of advertising (magazines, booklets, billboards...)
+Magazines and press articles illustration
+Decorations
+Creation of all kinds of professional printed documents
+
+VIDEO
+Decoration of TV shows, TV advertising...
+Movies illustrations or decorations
+Illustration of professional animated documents
+Illustration of web animations
+
+PRODUCTS
+Packaging creation
+Advertising products creation
+Creation of derivative products (posters, t-shirts...) intended for resale (Extended licenses)
+
+RESTRICTIONS
+All files proposed on Fotolia must be used in conformity with the following rules:
+Files must not be used in a way that places any person in the photo or the author in a bad light or depicts them in a way that they may find offensive (pornography, violence...)
+Files must not be associated to political parties or religious organizations.
+For security reasons, for web use, files must not be displayed in a size bigger than 640x480 pixels
+You need to write the copyright provided by Fotolia for all your uses.
+
+
+
+
+http://en.fotolia.com/Contract/View/XS
+
+CONTENT DOWNLOAD AGREEMENT (STANDARD LICENSE)
+No Sale
+Sublicense
+Restrictions
+Payments and Pricing
+Ownership and Retention of Rights
+Representations and Warranties
+Indemnification
+Limitations and Disclaimer
+Term and Termination
+Effect of Termination
+Miscellaneous
+This agreement (this "Agreement") shall be binding upon Fotolia LLC ("Fotolia") and any member (the "Non-Exclusive Downloading Member") who downloads a photograph, illustration, image or other pictorial or graphic work (the "Work") from the Fotolia.com website. The Non-Exclusive Downloading Member acknowledges and agrees that he or she shall be bound by the terms and conditions of this Agreement and that this Agreement applies to each Work that the Non-Exclusive Downloading Member downloads.
+1. No Sale
+The Non-Exclusive Downloading Member acknowledges and agrees that this Agreement does not effectuate any sale of the Work. Except for the rights specifically sublicensed under this Agreement, the Non-Exclusive Downloading Member shall not have any right, title or interest in or to, and in any event shall have no ownership of, the Work, including any copyright and other intellectual property rights.
+2. Sublicense
+Subject to the terms and conditions of this Agreement, Fotolia hereby grants to the Non-Exclusive Downloading Member a non-exclusive, perpetual, worldwide, non-transferable sublicense to use, reproduce or display the Work an unlimited number of times in the authorized media solely for (a) personal or educational purposes and (b) in connection with the operation of a business. However, the Non-Exclusive Downloading Member shall have no right to sell or distribute for sale the Work or any reproductions thereof, whether alone or incorporated or together with or onto any item of merchandise or other work of authorship, in any media or format now or hereafter known which primary value lies in the Work itself. The Non-Exclusive Downloading Member shall have no right to grant further sublicenses. The Non-Exclusive Downloading Member shall have the right to transfer files containing the Work or permitted derivative works to direct clients, customers, and employees, or have the Work
reproduced by subcontractors, provided that such subcontractors agree to abide by the restrictions of this agreement. In the normal course of workflow, the Non-Exclusive Downloading Member may also convey to a third party (such as a printer) temporary copies of the Work that are integral to the work product and without which the work product could not be completed. Third parties and subcontractors shall have no further or additional rights to use the Work and cannot access or extract it from any other file provided. The Non-Exclusive Downloading Member may create a digital library, network configuration or similar arrangement to allow the Work to be viewed by their employees, partners and clients. The Non-Exclusive Downloading Member shall pay to Fotolia a sublicense fee in accordance with Fotolia"s Standard pricing and payment policies . Notwithstanding anything to the contrary contained in this Agreement, with respect to electronic formats, the Non-Exclusive Downloading Me
mber"s reproduction, distribution or display of the Work shall be limited to a resolution of 640 ? 480 pixels in website uses (regardless of the resolution of the Work available for downloading from the Fotolia.com website), and shall be limited to the resolution available for downloading from the Fotolia.com website in other electronic uses. For clarification purposes but subject to the foregoing restrictions, it is intended that this sublicense shall permit use, reproduction and display of the Work in or for a business or commercial setting or circumstances, display in an office or other place of business, on advertising and promotion materials, and the like.
+In addition, the Non-Exclusive Downloading Member shall have the right to create modified and derivative works based upon the original Work (derivative works within the meaning of the USA Copyright Act which incorporates but is not substantially similar to the original Work ) . The permitted use of the modified and derivative works includes all the uses permitted to the Non-Exclusive Downloading Member with respect to the original work as well as for the derivative works in items for re-sale including t-shirts, mugs, calendars, posters mouse pads and alike
+3. Restrictions
+Notwithstanding anything to the contrary contained in this Agreement, and without limitation to any aforementioned restrictions, the Non-Exclusive Downloading Member acknowledges, agrees and warrants that he or she shall not:
+(a) sub-license, sell, assign, convey or transfer any of it"s rights under this agreement. Sell, license or distribute the Work or any modified Work as stand-alone files or as part of an online database or any other database, or any derivative product containing the Work in such way that would allow a third party to download, extract or access the Image as a stand-alone file;
+(b) share the Work with any other person or entity except as expressly permitted under this Agreement;
+(c) post the Work online in downloadable format, post the Work on an electronic bulletin board, or enable the Work to be distributed via mobile telephone devices. Include the Work in any electronic template or application, including those that are web based, where the purpose is to create multiple impressions of an electronic or printed product, including but not limited to website design, presentation templates, electronic greeting cards, business cards or any other electronic or printed matter;
+(d) download or store the Work on more than one computer at the same time, except that the Non-Exclusive Downloading Member may make a single backup copy to be stored on media separate from the single permitted computer;
+(e) use, reproduce, distribute or display the Work in connection with design template applications intended for resale;
+(f) use, reproduce, distribute or display the Work in connection with any goods or services intended for resale or distribution which primary value lies in the work itself, including, without limitation, mugs, t-shirts, posters, greeting cards, posters or other merchandise, and any of the foregoing in "print on demand" or tangible or electronic formats, as applicable;
+(g) use, reproduce, distribute or display the Work (including, without limitation, by itself or in combination with any other work of authorship) in any manner that is libelous or slanderous or otherwise defamatory, obscene or indecent;
+(h) remove any notice of copyright, trademark or other intellectual property right, or other information that may appear on, embedded in, or in connection with the Work in its original downloaded form, it being understood that the Non-Exclusive Downloading Member shall reproduce any and all such notices in any backup copy of the file comprising the Work that the Downloading Member makes;
+(i) incorporate the Work into a trademark or service mark;
+(j) take any action in connection with the Work that violates any law, regulation or statute in an applicable jurisdiction;
+(k) Use the Work in an editorial manner, without the following credit adjacent to the Image: "© [Photographer's name] / [Name of the agency providing the Image].;
+(l) take any action in connection with the Work that violates or infringes the intellectual property or other rights of any person or entity, including, without limitation, the moral rights of the creator of the Work and the rights of any person who, or any person whose property, appears in the Work; or
+(m) take any action in connection with the Work that associates it or the creator of the Work, or the persons or property appearing in the Work (if any), with any political, religious, economic or other opinion-based movements or parties.
+(n) use the Work in a way that places any person in the photo in a bad light or depicts them in a way that they may find offensive - this includes, but is not limited to:
+(1) the use of Images in pornography;
+(2) tobacco ads;
+(3) ads for adult entertainment clubs or similar venues, or for escort, dating or similar services;
+(4) political endorsements;
+(5) uses that are defamatory, or contain otherwise unlawful, offensive or immoral content.
+4. Payments and Pricing
+As indicated above, the Non-Exclusive Downloading Member shall pay to Fotolia a sub-license fee in accordance with Fotolia's Standard pricing and payment policies .
+5. Ownership and Retention of Rights
+The Non-Exclusive Downloading Member acknowledges and agrees that Fotolia and/or its licensor retains all rights, title and interest in and to the Work (except for the rights granted pursuant to this Agreement), and that neither title nor any ownership interest in or to the Work is transferred to the Non-Exclusive Downloading Member by virtue of this Agreement. Fotolia and/or its licensor (as applicable) shall also retain the right to use, reproduce or display the Work solely to demonstrate the Work as part of his or her professional portfolio. Without any limitation to any other rights that Fotolia may retain, Fotolia shall continue to have the right to use the Work for internal archival and reference purposes.
+6. Representations and Warranties
+In addition to the representations and warranties made by the Non-Exclusive Downloading Member above, each of Fotolia and the Non-Exclusive Downloading Member hereby represent and warrant that it, or he or she, has the right to enter into this Agreement.
+7. Indemnification
+The Non-Exclusive Downloading Member agrees to indemnify, defend and hold harmless Fotolia and its affiliates, and their respective officers, directors, employees, owners, agents, representatives, licensors and (sub)licensees (collectively, "Indemnitees") from and against all claims, expenses (including attorney fees) or other liability arising from the Non-Exclusive Downloading Member"s breach of any of his or her representations, warranties or obligations under this Agreement, and from any and all uses of the Work, including, without limitation, any claims or actions based on infringement or violation of intellectual property rights, libel or slander or other defamation, right of privacy or "false light", right of publicity or blurring or distortion or alteration whether or not intentional. Fotolia shall have the right, in its sole discretion, to control the defense of any claim, action or matter subject to indemnification by the Non-Exclusive Downloading Member with couns
el of its own choosing. The Non-Exclusive Downloading Member shall fully cooperate with Fotolia in the defense of any such claim, action or matter.
+8. Limitations and Disclaimer
+The Non-Exclusive Downloading Member agrees that neither Fotolia nor its affiliates, nor any of their respective officers, directors, employees, owners, agents, representatives, licensors and (sub)licensees (other than the Downloading Member), shall be liable for any damages, whether direct, incidental, indirect or consequential, arising from any use or non-use of the Work, even if such parties have been advised, or advised of the possibility, of such damages.
+The Non-Exclusive Downloading Member acknowledges that Fotolia generally does not have releases for the trademarks, logos or other intellectual property of other parties that may be depicted in some Works. The procuring of such releases is the responsibility of the Non-Exclusive Downloading Member.
+The Non-Exclusive Downloading Member acknowledges that Fotolia generally does not have releases from property owners, manufacturers or designers of commercial products such as (without limitation) automobiles, aircraft, packaged products, designer clothing, etc. that are depicted in some Works. It is generally not possible for any stock image library or artist to get blanket releases for such products, but they can often be obtained on a case-by-case basis. The procuring of such releases is the responsibility of the Non-Exclusive Downloading Member.
+THE WORK IS PROVIDED "AS IS" AND, EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER PARTY MAKES ANY REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
+9. Term and Termination
+This Agreement shall continue in perpetuity unless terminated in accordance with this Section 9. Fotolia may at any time terminate this Agreement with respect to any Work in the event of any breach by the Non-Exclusive Downloading Member of any of his or her representations, warranties or obligations under this Agreement. The Non-Exclusive Downloading Member may at any time terminate this Agreement. Each of Fotolia and the Non-Exclusive Downloading Member shall notify the other in the event it, he or she terminates this Agreement. Fotolia shall also have the right, in its sole discretion, to deny the downloading of any Work from the Fotolia.com website. Upon termination of a license for any particular Work, the Non-Exclusive Downloading Member shall immediately cease using such Work, destroy, or upon the request of Fotolia return the Work to Fotolia, delete or remove the Work from its premises, computer systems and storage (electronic and physical), and shall ensure that its
clients and customers do likewise.
+10. Effect of Termination
+Upon the termination of this Agreement, the Non-Exclusive Downloading Member shall cease using the Work and destroy all copies of the Work, and all derivative works and related materials (if any), in his or her possession or control. At Fotolia"s request, the Non-Exclusive Downloading Member shall certify in writing to such destruction of the Work, derivative works and/or related materials. Termination of this Agreement shall not relieve the Non-Exclusive Downloading Member from any payment obligations that may have arisen prior to such termination. The provisions of Sections 1, 4, 5, 6, 7, 8, 10 and 11 shall survive the termination of this Agreement.
+11. Miscellaneous
+This Agreement shall be governed by and construed in accordance with the laws of the State of New York, without regard to any conflict of laws principles. Any legal action, suit or proceeding arising out of or relating to this Agreement shall be instituted in a court of competent subject matter jurisdiction in the federal or state courts of the State of New York, and the Non-Exclusive Downloading Member and Fotolia each submit to the personal jurisdiction of such court and waive any right each might otherwise have to claim lack of personal jurisdiction or inconvenience of forum.
+The relationship between Fotolia and the Non-Exclusive Downloading Member under this Agreement is that of independent contractors. For clarification purposes, the parties are not joint ventures, partners, principal and agent, or employer and employee. Neither party shall have the power to bind or obligate the other in any manner.
+The Non-Exclusive Downloading Member agrees that he or she shall be responsible for all use, sales, value-added and similar taxes and duties imposed by any governing authority in any jurisdiction in connection with the license granted to him or her under this Agreement.
+No waiver on the part of Fotolia to exercise any power, right, privilege or remedy under this Agreement, and no delay on the part of Fotolia to exercise any such power, right, privilege or remedy, shall preclude any other or further exercise thereof or of any other power, right, privilege or remedy.
+Except with respect to any trademark rights, all rights and licenses granted by Fotolia under or pursuant to this Agreement are for all purposes of Section 365(n) of Title 11 of the United States Code ("Title 11"), licenses of rights to "intellectual property" as defined in Title 11. Fotolia agrees that, in the event of commencement of bankruptcy proceedings by or against Fotolia under Title 11, the Non-Exclusive Downloading Member, as licensee of such rights under this Agreement, shall retain and may fully exercise all of its rights under this Agreement (including the license granted under this Agreement) and all of its rights and elections under Title 11.
+Fotolia shall have the right, in its sole discretion, to assign any or all of its rights or obligations under this Agreement. The Non-Exclusive Downloading Member shall have no right to assign any of his or her rights or obligations under this Agreement.
+This Agreement shall be inure to the benefit of, and be binding upon, Fotolia and the Non-Exclusive Downloading Member, and their respective successors and assigns. Nothing in this Agreement, express or implied, is intended to confer upon any person or entity, other than Fotolia and the Non-Exclusive Downloading Member, and their respective successors and assigns, any rights, remedies, obligations or liabilities under or by reason of this Agreement.
+Whenever the context so requires, the singular number shall include the plural and vice versa, and the masculine, feminine and neutral genders shall include each other.
+If any term or provision of this Agreement is invalid, illegal or unenforceable, all other terms and conditions of this Agreement shall nevertheless remain in full force and effect.
+The underlined headings contained in this Agreement are for convenience of reference only and shall not affect in any way the meaning or interpretation of this Agreement
+
Propchange: bval/cms-site/content/images/Fotolia_License.txt
------------------------------------------------------------------------------
svn:eol-style = native
Added: bval/cms-site/content/images/apache-incubator-logo.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/apache-incubator-logo.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/apache-incubator-logo.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/beanvalidation_logo.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/beanvalidation_logo.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/beanvalidation_logo.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/bg.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/bg.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/bg.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/bg02-banner-left.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/bg02-banner-left.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/bg02-banner-left.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/bg02-banner-right.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/bg02-banner-right.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/bg02-banner-right.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/bg02-white-left-nogr.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/bg02-white-left-nogr.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/bg02-white-left-nogr.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/bg02-white-right-nogr.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/bg02-white-right-nogr.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/bg02-white-right-nogr.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/bval_logo.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/bval_logo.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/bval_logo.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/check3_236x250.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/check3_236x250.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/check3_236x250.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/check3_236x250.psd
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/check3_236x250.psd?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/check3_236x250.psd
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: bval/cms-site/content/images/check3_71x75.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/check3_71x75.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/check3_71x75.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/check3_94x100.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/check3_94x100.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/check3_94x100.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/feather-small.gif
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/feather-small.gif?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/feather-small.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: bval/cms-site/content/images/left-box-bottom.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/left-box-bottom.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/left-box-bottom.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/left-box-right.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/left-box-right.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/left-box-right.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/left-box-top.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/left-box-top.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/left-box-top.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/images/logo.png
URL: http://svn.apache.org/viewvc/bval/cms-site/content/images/logo.png?rev=1299018&view=auto
==============================================================================
Binary file - no diff available.
Propchange: bval/cms-site/content/images/logo.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: bval/cms-site/content/index.cwiki
URL: http://svn.apache.org/viewvc/bval/cms-site/content/index.cwiki?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/index.cwiki (added)
+++ bval/cms-site/content/index.cwiki Fri Mar 9 20:14:15 2012
@@ -0,0 +1,23 @@
+h2. Welcome to the Apache BVal project
+
+{section}
+
+{column:width=60%}
+Apache BVal delivers an implementation of the [Bean Validation Specification (JSR303)|http://jcp.org/en/jsr/detail?id=303], which is TCK compliant and works on Java SE 5 or later. The initial codebase for the project was donated to the ASF by a SGA from Agimatec GmbH and uses the Apache Software License v2.0. After a successful [incubation|http://incubator.apache.org], Apache BVal became a top-level project of the ASF on February 15, 2012.
+
+{column}
+
+{column:width=40%}
+!http://people.apache.org/~dwoods/bval/images/check3_236x250.png|align=center!
+{column}
+
+{section}
+
+
+h2. Recent News
+
+\\
+
+{blog-posts:max=5}
+
+\\
Added: bval/cms-site/content/index.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/content/index.mdtext?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/index.mdtext (added)
+++ bval/cms-site/content/index.mdtext Fri Mar 9 20:14:15 2012
@@ -0,0 +1,33 @@
+Title: Index
+<a name="Index-WelcometotheApacheBValproject"></a>
+## Welcome to the Apache BVal project
+
+Apache BVal delivers an implementation of the
+[Bean Validation Specification (JSR303)](http://jcp.org/en/jsr/detail?id=303),
+which is TCK compliant and works on Java SE 5 or later. The initial
+codebase for the project was donated to the ASF by a SGA from Agimatec GmbH
+and uses the Apache Software License v2.0. After a successful
+[incubation](http://incubator.apache.org),
+Apache BVal became a top-level project of the ASF on February 15, 2012.
+
+<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.6.1/jquery.min.js"; type="text/javascript"></script>
+<script type="text/javascript">
+ $(function() {
+ var limit = 5;
+ getBlogEntries("https://cwiki.apache.org/confluence",
+ "BeanValidation", limit, $("newsItem-prototype"), $("newsItemList"));
+ });
+});
+</script>
+<div id="recentNews" style="display: none;">
+ <a name="Index-RecentNews"></a>
+## Recent News
+
+ <ul id="newsItemList">
+ <li id="newsItem-prototype" style="display: none;">
+ <div class="date" />
+ <div class="title" />
+ <div class="detail" />
+ </li>
+ </ul>
+</div>
Added: bval/cms-site/content/jsr303-tck.cwiki
URL: http://svn.apache.org/viewvc/bval/cms-site/content/jsr303-tck.cwiki?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/jsr303-tck.cwiki (added)
+++ bval/cms-site/content/jsr303-tck.cwiki Fri Mar 9 20:14:15 2012
@@ -0,0 +1,46 @@
+h3. How to obtain the TCK for testing
+
+The JSR303 Bean Validation TCK was created by Red Hat/JBoss and is available under the ASL 2.0 license, which allows anyone to download and run the TCK without having to sign the Sun/ASF NDA.
+
+Please see the [Bean Validation TCK|http://community.jboss.org/wiki/BeanValidationTCK] website for details on how to setup a local JBoss instance for running the TCK. The /bval-tck module should be used to execute the TCK in JBoss against our implementation.
+
+\\
+
+h3. Steps to run the TCK against our implementation
+
+For the below build and TCK runs, I'm assuming you have the latest Sun 1.6.0 JDK installed and set as the default Java implementation.
+
+h4. Stand-alone
+
+# Build the project and run the junits -
+{code}
+cd bval/trunk
+mvn clean install
+{code}
+# Run the JBoss provided TCK in stand-alone mode -
+{code}
+cd bval/trunk/bval-tck
+mvn -Ptck
+{code}
+
+h4. In-container
+
+# Build the project and run the junits -
+{code}
+cd bval/trunk
+mvn clean install
+{code}
+# Download and extract a copy of the jboss-5.1.0.GA-jdk6.zip file (for Java SE 6 users) from [http://sourceforge.net/projects/jboss/files/JBoss/JBoss-5.1.0.GA/]
+# Run the JBoss provided TCK in the in-container mode, against your local copy of JBoss 5.1.0.GA (where $jboss510home=/opt/jboss-5.1.0.GA/ below) -
+{code}
+cd bval/trunk/bval-tck
+mvn -Ptck,incontainer -Djboss.home=$jboss510home
+{code}
+
+\\
+
+h3. Certification against the JCP provided TCK
+
+TBD - Need to ask if we must use the Sun/Oracle provided TCK for final certification testing....
+
+\\
Added: bval/cms-site/content/jsr303-tck.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/content/jsr303-tck.mdtext?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/jsr303-tck.mdtext (added)
+++ bval/cms-site/content/jsr303-tck.mdtext Fri Mar 9 20:14:15 2012
@@ -0,0 +1,60 @@
+Title: JSR303 TCK
+<a name="JSR303TCK-HowtoobtaintheTCKfortesting"></a>
+### How to obtain the TCK for testing
+
+The JSR303 Bean Validation TCK was created by [Red Hat/JBoss][jboss] and is
+available under the [Apache License, version 2.0][ALv2], which allows anyone
+to download and run the TCK without having to sign the Sun/ASF NDA.
+
+Please see the
+[Bean Validation TCK](http://community.jboss.org/wiki/BeanValidationTCK)
+website for details on how to setup a local JBoss instance for running the TCK.
+The `bval-tck` module should be used to execute the TCK against Apache BVal.
+
+<a name="JSR303TCK-StepstoruntheTCKagainstourimplementation"></a>
+### Steps to run the TCK
+
+For the below build and TCK runs, it is assumed that you have the latest Sun
+1.6.0 JDK installed and set as the default Java implementation.
+
+<a name="JSR303TCK-Standalone"></a>
+#### Standalone
+
+1. Build the project and run the [JUnit][] tests:
+
+ :::sh
+ cd bval/trunk
+ mvn clean install
+
+1. Run the JBoss provided TCK in standalone mode -
+
+ :::sh
+ cd bval/trunk/bval-tck
+ mvn -Ptck
+
+<a name="JSR303TCK-In-container"></a>
+#### In-container
+
+1. Build the project and run the [JUnit][] tests:
+
+ :::sh
+ cd bval/trunk
+ mvn clean install
+
+1. Install [JBoss Application Server](http://www.jboss.org/jbossas); version
+ 5.1.0 or later.
+1. Run the JBoss provided TCK in the in-container mode, against your JBoss AS
+ installation (where `$jbosshome` denotes the installation path):
+
+ :::sh
+ cd bval/trunk/bval-tck
+ mvn -Ptck,incontainer -Djboss.home=$jbosshome
+
+<a name="JSR303TCK-CertificationagainsttheJCPprovidedTCK"></a>
+### Certification against the JCP provided TCK
+
+*TBD* - Must we use the Sun/Oracle provided TCK for final certification testing?
+
+[ALv2]: http://www.apache.org/licenses/LICENSE-2.0
+[junit]: http://junit.org
+[jboss]: http://www.jboss.org/
Added: bval/cms-site/content/mailing-lists.cwiki
URL: http://svn.apache.org/viewvc/bval/cms-site/content/mailing-lists.cwiki?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/mailing-lists.cwiki (added)
+++ bval/cms-site/content/mailing-lists.cwiki Fri Mar 9 20:14:15 2012
@@ -0,0 +1,25 @@
+The BVal User list is for general discussion or questions on using our JSR-303 implementation. Committers and other users monitor this list and provide assistance when needed.
+
+ * [Subscribe|mailto:user-subscribe@bval.apache.org] to the BVal User list
+ * [Unsubscribe|mailto:user-unsubscribe@bval.apache.org] from the BVal User list
+ * [Post|mailto:user@bval.apache.org] to the BVal User list
+ * View the BVal User list archives:
+ ** [Current|http://mail-archives.apache.org/mod_mbox/bval-user/]
+ ** [Incubation|http://mail-archives.apache.org/mod_mbox/incubator-bval-user/]
+
+The BVal Developer list is for developers to discuss ongoing work, make decisions and vote on technical issues.
+
+ * [Subscribe|mailto:dev-subscribe@bval.apache.org] to the BVal Dev list
+ * [Unsubscribe|mailto:dev-unsubscribe@bval.apache.org] from the BVal Dev list
+ * [Post|mailto:dev@bval.apache.org] to the BVal Dev list
+ * View the BVal Dev list archives:
+ ** [Current|http://mail-archives.apache.org/mod_mbox/bval-dev/]
+ ** [Incubation|http://mail-archives.apache.org/mod_mbox/incubator-bval-dev/]
+
+The BVal Commits list receives notifications when changes are committed to the Bean Validation source tree.
+
+ * [Subscribe|mailto:commits-subscribe@bval.apache.org] to the BVal Commits list
+ * [Unsubscribe|mailto:commits-unsubscribe@bval.apache.org] from the BVal Commits list
+ * View the BVal Commits list archives:
+ ** [Current|http://mail-archives.apache.org/mod_mbox/bval-commits/]
+ ** [Incubation|http://mail-archives.apache.org/mod_mbox/incubator-bval-commits/]
Added: bval/cms-site/content/mailing-lists.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/content/mailing-lists.mdtext?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/mailing-lists.mdtext (added)
+++ bval/cms-site/content/mailing-lists.mdtext Fri Mar 9 20:14:15 2012
@@ -0,0 +1,32 @@
+Title: Mailing Lists
+The BVal User list is for general discussion or questions on using our
+JSR-303 implementation. Committers and other users monitor this list and
+provide assistance when needed.
+
+ * [Subscribe](mailto:user-subscribe@bval.apache.org.html)
+ to the BVal User list
+ * [Unsubscribe](mailto:user-unsubscribe@bval.apache.org.html)
+ from the BVal User list
+ * [Post](mailto:user@bval.apache.org.html)
+ to the BVal User list
+ * View the BVal User list archives: [Current](http://mail-archives.apache.org/mod_mbox/bval-user/), [Incubation](http://mail-archives.apache.org/mod_mbox/incubator-bval-user/)
+
+The BVal Developer list is for developers to discuss ongoing work, make
+decisions and vote on technical issues.
+
+ * [Subscribe](mailto:dev-subscribe@bval.apache.org.html)
+ to the BVal Dev list
+ * [Unsubscribe](mailto:dev-unsubscribe@bval.apache.org.html)
+ from the BVal Dev list
+ * [Post](mailto:dev@bval.apache.org.html)
+ to the BVal Dev list
+ * View the BVal Dev list archives: [Current](http://mail-archives.apache.org/mod_mbox/bval-dev/), [Incubation](http://mail-archives.apache.org/mod_mbox/incubator-bval-dev/)
+
+The BVal Commits list receives notifications when changes are committed to
+the Bean Validation source tree.
+
+ * [Subscribe](mailto:commits-subscribe@bval.apache.org.html)
+ to the BVal Commits list
+ * [Unsubscribe](mailto:commits-unsubscribe@bval.apache.org.html)
+ from the BVal Commits list
+ * View the BVal Commits list archives: [Current](http://mail-archives.apache.org/mod_mbox/bval-commits/), [Incubation](http://mail-archives.apache.org/mod_mbox/incubator-bval-commits/)
Added: bval/cms-site/content/obtaining-a-validator.cwiki
URL: http://svn.apache.org/viewvc/bval/cms-site/content/obtaining-a-validator.cwiki?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/obtaining-a-validator.cwiki (added)
+++ bval/cms-site/content/obtaining-a-validator.cwiki Fri Mar 9 20:14:15 2012
@@ -0,0 +1,179 @@
+To obtain a validator, you must first create a ValidatorFactory. If there is only one jsr303 implementation in your classpath, you can use:
+
+{code:java}
+ValidatorFactory vf = Validation.buildDefaultValidatorFactory();
+{code}
+
+to obtain the factory. If there are various implementations in the classpath, or you want to be sure you are using the Apache one, you can use:
+
+{code:java}
+ValidatorFactory avf = Validation.byProvider(ApacheValidationProvider.class).configure().buildValidatorFactory();
+{code}
+
+You should not instantiate more than one factory, as factory creation is a costly process and the factory also acts as a constraint cache for the validators.
+
+Once you have a ValidatorFactory, obtaining a validator just requires you to call {{ValidatorFactory#getValidator()}}. The validator implementation is thread-safe, so you can choose to re-use a single instance of it in all your code or create validators on demand: both options are fine and should perform equally well.
+
+Below is an example that will create a singleton ValidatorFactory and will let you obtain validators from it:
+
+{code:java}
+public enum MyValidatorFactory {
+
+ SINGLE_INSTANCE {
+
+ ValidatorFactory avf = Validation.byProvider(ApacheValidationProvider.class).configure().buildValidatorFactory();
+
+ @Override
+ public Validator getValidator() {
+ return avf.getValidator();
+ }
+
+ };
+
+ public abstract Validator getValidator();
+}
+{code}
+
+Using the above class, obtaining a validator just requires you to call: {{MyValidatorFactory.SINGLE_INSTANCE.getValidator()}}
+
+
+h3. Using Spring
+
+If you are using Spring, you can easily inject validators in your beans. Simply configure the factory in your applicationContext by adding:
+
+{code:xml}
+ <!-- Validator bean -->
+ <bean id="validator" class="org.springframework.validation.beanvalidation.LocalValidatorFactoryBean">
+ <property name="providerClass" value="org.apache.bval.jsr303.ApacheValidationProvider" />
+ </bean>
+{code}
+
+And Spring will be able to inject Validators and the ValidatorFactory in your beans.
+
+h3. Using Google Guice
+
+_Apache BVal_ provides the {{bval-guice}} module that simplifies integration with _Google Guice_. That module has multiple purposes, such:
+
+* bootstrap _Apache BVal_ using _Google Guice_;
+* obtain _javax.validation.ConstraintValidator_ instances using the _Google Guice Injector_, to easily support the DI;
+* easily inject the _javax.validation.Validator_ reference into components that require it;
+* easily intercept methods and validate method arguments.
+
+First of all, users have to add the {{bval-guice}} module in the classpath; _Apache Maven_ users can easily include it just by adding the following dependency in the POM:
+
+{code:xml}
+<dependency>
+ <groupId>org.apache.bval</groupId>
+ <artifactId>bval-guice</artifactId>
+ <version>0.3-incubating</version>
+</dependency>
+{code}
+
+Let's have a look at the features:
+
+h5. Apache BVal bootstrapping
+
+Simply, the {{org.apache.bval.guice.ValidationModule}} is the _Google Guice_ module that bootstraps _Apache BVal_; all users have to do is add this module when creating the _Google Guice Injector_:
+
+{code:java}
+import com.google.inject.Guice;
+import com.google.inject.Injector;
+
+import org.apache.bval.guice.ValidationModule;
+
+Injector injector = Guice.createInjector([...], new ValidationModule(), [...]);
+{code}
+
+h5. obtain _javax.validation.ConstraintValidator_ instances
+
+Users can implement now _javax.validation.ConstraintValidator_ classes that require _Dependency Injection_ by _Google Guice_:
+
+{code:java}
+import javax.validation.ConstraintValidator;
+
+public class MyCustomValidator implements ConstraintValidator<MyAssert, MyType> {
+
+ private final MyExternalService service;
+
+ @Inject
+ public MyCustomValidator(MyExternalService service) {
+ this.service = service;
+ }
+
+ public void initialize(MyAssert annotation) {
+ // do something
+ }
+
+ public boolean isValid(MyType value, ConstraintValidatorContext context) {
+ return value == null || this.service.doSomething(value);
+ }
+
+}
+{code}
+
+Don't forget to bind the {{MyExternalService}} class in the _Google Guice Bincer_!!!
+
+h5. Inject the _javax.validation.Validator_ reference
+
+Clients can easily inject {{javax.validation.Validator}} instances into their custom components just marking it using the _Google Guice Inject_ annotation:
+
+{code:java}
+import javax.validation.Validator;
+
+public class MyValidatorClient {
+
+ @Inject
+ private Validator validator;
+
+ public void setValidator(Validator validator) {
+ this.validator = validator;
+ }
+
+ ...
+
+}
+{code}
+
+When obtaining {{MyValidatorClient}} instances from the _Injector_, the {{javax.validation.Validator}} will be automagically bound.
+
+h5. Intercept methods and validate method arguments
+
+Taking advantage from the _Apache BVal_ extension to validate method arguments, the {{bval-guice}} comes with an _AOP_ interceptor - automatically initialized in the {{org.apache.bval.guice.ValidationModule}} - that makes easier the methods arguments validation.
+
+All users have to do is annotate interested methods with {{org.apache.bval.guice.Validate}} annotation, then annotate arguments with constraints, as follows below:
+
+{code:java}
+import javax.validation.constraints.NotNull;
+import javax.validation.constraints.Size;
+
+import org.apache.bval.guice.Validate;
+
+public class MyService {
+
+ @Validate(
+ groups = { MyGroup.class },
+ validateReturnedValue = true
+ )
+ public Country insertCountry(@NotNull(groups = { MyGroup.class })
+ String name,
+ @NotNull(groups = { MyGroup.class })
+ @Size(max = 2, groups = { MyGroup.class, MyOtherGroup.class })
+ String iso2Code,
+ @NotNull(groups = { MyGroup.class })
+ @Size(max = 3, groups = { MyGroup.class, MyOtherGroup.class })
+ String iso3Code) {
+
+ return ...;
+ }
+
+}
+{code}
+
+The {{org.apache.bval.guice.Validate}} supports 2 parameters:
+
+* {{groups}} Class array, _empty_ by default, that marks the groups have to be validated;
+* {{validateReturnedValue}} flag, _false_ by default, that marks that if the returned object by the method execution has to be validated.
+
+h3. Using CDI
+
+We recommend [MyFaces CODI|http://myfaces.apache.org/extensions/cdi/index.html].
\ No newline at end of file
Added: bval/cms-site/content/obtaining-a-validator.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/content/obtaining-a-validator.mdtext?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/obtaining-a-validator.mdtext (added)
+++ bval/cms-site/content/obtaining-a-validator.mdtext Fri Mar 9 20:14:15 2012
@@ -0,0 +1,223 @@
+Title: Obtaining a validator
+To obtain a `Validator`, you must first create a `ValidatorFactory`. If there
+is only one Bean Validation implementation in your classpath, you can use:
+
+ :::java
+ ValidatorFactory vf = Validation.buildDefaultValidatorFactory();
+
+to obtain the factory. If there are various implementations in the
+classpath, or you want to be sure you are using Apache BVal, you can
+use:
+
+ :::java
+ ValidatorFactory avf =
+ Validation.byProvider(ApacheValidationProvider.class).configure().buildValidatorFactory();
+
+You should usually not instantiate more than one factory; factory creation is a
+costly process. Also, the factory also acts as a cache for the available
+validation constraints.
+
+Once you have a ValidatorFactory, obtaining a validator just requires you
+to call `ValidatorFactory#getValidator()`. The validator implementation
+is thread-safe, so you can choose to re-use a single instance of it in all
+your code or create validators on demand: both options should
+perform equally well.
+
+Below is an example that will create a singleton `ValidatorFactory` and will
+let you obtain `Validator`s from it:
+
+ :::java
+ public enum MyValidatorFactory {
+
+ SINGLE_INSTANCE {
+
+ ValidatorFactory avf =
+ Validation.byProvider(ApacheValidationProvider.class).configure().buildValidatorFactory();
+
+ @Override
+ public Validator getValidator() {
+ return avf.getValidator();
+ }
+
+ };
+
+ public abstract Validator getValidator();
+ }
+
+Using the above class, obtaining a `Validator` just requires you to call:
+
+ :::java
+ MyValidatorFactory.SINGLE_INSTANCE.getValidator()
+
+<a name="Obtainingavalidator-UsingSpring"></a>
+### Using [The Spring Framework][spring]
+
+If you are using Spring, you can easily inject `Validator`s into your beans.
+Simply configure the factory in your `ApplicationContext` by adding:
+
+ :::xml
+ <!-- Validator bean -->
+ <bean id="validator"
+ class="org.springframework.validation.beanvalidation.LocalValidatorFactoryBean">
+ <property name="providerClass"
+ value="org.apache.bval.jsr303.ApacheValidationProvider" />
+ </bean>
+
+And Spring will be able to inject `Validator`s and the `ValidatorFactory` into
+your beans.
+
+<a name="Obtainingavalidator-UsingGoogleGuice"></a>
+### Using Google Guice
+
+Apache BVal provides the `bval-guice` module that simplifies
+integration with [Google Guice][guice]. That module has multiple purposes, such:
+
+* bootstrap Apache BVal using Google Guice;
+* obtain `javax.validation.ConstraintValidator` instances using the Google
+Guice `Injector` to easily support DI;
+* easily inject the `javax.validation.Validator` reference into components
+that require it;
+* easily intercept methods and validate method arguments.
+
+First of all, users have to add the `bval-guice` module in the classpath;
+[Apache Maven][maven] users can easily include it just by adding the following
+dependency in the POM:
+
+ :::xml
+ <dependency>
+ <groupId>org.apache.bval</groupId>
+ <artifactId>bval-guice</artifactId>
+ <version>0.3-incubating</version>
+ </dependency>
+
+Let's have a look at the features:
+
+<a name="Obtainingavalidator-ApacheBValbootstrapping"></a>
+##### Bootstrapping Apache BVal
+
+Simply, the `org.apache.bval.guice.ValidationModule` is the Google
+Guice module that bootstraps Apache BVal. All users have to do is add
+this module when creating the Google Guice `Injector`:
+
+ :::java
+ import com.google.inject.Guice;
+ import com.google.inject.Injector;
+
+ import org.apache.bval.guice.ValidationModule;
+
+ Injector injector = Guice.createInjector([...](....html),
+ new ValidationModule(), [...]
+ );
+
+##### Obtain `javax.validation.ConstraintValidator` instances
+
+Users can now implement `javax.validation.ConstraintValidator` classes that
+require _Dependency Injection_ by Google Guice:
+
+ :::java
+ import javax.validation.ConstraintValidator;
+
+ public class MyCustomValidator implements ConstraintValidator<MyAssert, MyType> {
+
+ private final MyExternalService service;
+
+ @Inject
+ public MyCustomValidator(MyExternalService service) {
+ this.service = service;
+ }
+
+ public void initialize(MyAssert annotation) {
+ // do something
+ }
+
+ public boolean isValid(MyType value, ConstraintValidatorContext context) {
+ return value == null || this.service.doSomething(value);
+ }
+ }
+
+Don't forget to bind the `MyExternalService` class in the Google Guice
+`Binder`!!!
+
+<a name="Obtainingavalidator-Injectthe_javax.validation.Validator_reference"></a>
+##### Inject the `javax.validation.Validator` reference
+
+Clients can easily inject `javax.validation.Validator` instances into
+their custom components just marking it using the Google Guice `@Inject`
+annotation:
+
+ :::java
+ import javax.validation.Validator;
+
+ public class MyValidatorClient {
+
+ @Inject
+ private Validator validator;
+
+ public void setValidator(Validator validator) {
+ this.validator = validator;
+ }
+
+ // ...
+
+ }
+
+When obtaining `MyValidatorClient` instances from the `Injector`, the
+`javax.validation.Validator` will be automagically bound.
+
+##### Intercept methods and validate method arguments
+
+Taking advantage of the Apache BVal extension to validate method
+arguments, the `bval-guice` module comes with an _AOP_ interceptor,
+automatically initialized in the `org.apache.bval.guice.ValidationModule`,
+that facilitates the validation of method arguments.
+
+All users have to do is annotate interested methods with
+`org.apache.bval.guice.Validate` annotation, then annotate arguments with
+constraints, as follows below:
+
+ :::java
+ import javax.validation.constraints.NotNull;
+ import javax.validation.constraints.Size;
+
+ import org.apache.bval.guice.Validate;
+
+ public class MyService {
+
+ @Validate(
+ groups = { MyGroup.class },
+ validateReturnedValue = true
+ )
+ public Country insertCountry(@NotNull(groups = { MyGroup.class })
+ String name,
+ @NotNull(groups = { MyGroup.class })
+ @Size(max = 2, groups = { MyGroup.class, MyOtherGroup.class })
+ String iso2Code,
+ @NotNull(groups = { MyGroup.class })
+ @Size(max = 3, groups = { MyGroup.class, MyOtherGroup.class })
+ String iso3Code) {
+
+ return ...;
+ }
+
+ }
+
+The `bval-guice @Validate` annotation supports 2 values:
+
+* `groups` Class array, `{}` by default, that specifies the groups to be validated;
+* `validateReturnedValue` flag, `false` by default, indicating whether
+the method's return value should be validated.
+
+<a name="Obtainingavalidator-UsingCDI"></a>
+### Using CDI
+
+Bean Validation integration with [CDI][] is provided by:
+
+* The Bean Validation integration module of [MyFaces CODI][]
+* [Seam Validation Module][]
+
+[guice]: http://code.google.com/p/google-guice/
+[spring]: http://www.springsource.org
+[maven]: http://maven.apache.org
+[cdi]: http://jcp.org/en/jsr/summary?id=299
+[MyFaces CODI]: http://myfaces.apache.org/extensions/cdi/index.html
+[seam validation module]: http://seamframework.org/Seam3/ValidationModule
Added: bval/cms-site/content/overview.cwiki
URL: http://svn.apache.org/viewvc/bval/cms-site/content/overview.cwiki?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/overview.cwiki (added)
+++ bval/cms-site/content/overview.cwiki Fri Mar 9 20:14:15 2012
@@ -0,0 +1 @@
+{children}
\ No newline at end of file
Added: bval/cms-site/content/overview.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/content/overview.mdtext?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/overview.mdtext (added)
+++ bval/cms-site/content/overview.mdtext Fri Mar 9 20:14:15 2012
@@ -0,0 +1,2 @@
+Title: Overview
+{children}
Added: bval/cms-site/content/people.cwiki
URL: http://svn.apache.org/viewvc/bval/cms-site/content/people.cwiki?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/people.cwiki (added)
+++ bval/cms-site/content/people.cwiki Fri Mar 9 20:14:15 2012
@@ -0,0 +1,19 @@
+This is a list of the people involved in Apache BVal and their roles.
+
+||Name||Id||Organization||PMC Member||PMC chair||
+| Albert Lee | allee8285 | | (/) | |
+| Carlos Vara | carlosvara | Amazon | (/) | |
+| David Jencks | djencks | IBM | (/) | |
+| Donald Woods | dwoods | IBM | (/) | |
+| Gerhard Petracek | gpetracek | IRIAN Solutions GmbH | (/) | |
+| Jeremy Bauer | jrbauer | IBM | (/) | |
+| Kevan Miller | kevan | IBM | (/) | |
+| Luciano Resende | lresende | IBM | (/) | |
+| Mark Struberg | struberg | | (/) | |
+| Matt Benson | mbenson | Permanent General Assurance Corp | (/) | (/) |
+| Matthias Wessendorf | matzew | Kaazing | (/) | |
+| Mohammad Nour El-Din | mnour | Thebe Technology | (/) | |
+| Roman Stumm | romanstumm | Agimatec GmbH | (/) | |
+| Simone Tripodi | simonetripodi | | (/) | |
+
+Apache BVal would like specifically to thank its incubation champion and mentor Kevan Miller. Thanks go also to mentors Luciano Resende, Matthias Wessendorf, and Niall Pemberton.
\ No newline at end of file
Added: bval/cms-site/content/people.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/content/people.mdtext?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/people.mdtext (added)
+++ bval/cms-site/content/people.mdtext Fri Mar 9 20:14:15 2012
@@ -0,0 +1,25 @@
+Title: People
+This is a list of the people involved in Apache BVal and their roles.
+
+Name | Id | Organization | PMC Member | PMC chair
+---- | -- | ------------ | ---------- | ---------
+Albert Lee | allee8285 | | ![X][X]
+Carlos Vara | carlosvara | Amazon | ![X][X]
+David Jencks | djencks | IBM | ![X][X]
+Donald Woods | dwoods | IBM | ![X][X]
+Gerhard Petracek | gpetracek | IRIAN Solutions GmbH | ![X][X]
+Jeremy Bauer | jrbauer | IBM | ![X][X]
+Kevan Miller | kevan | IBM | ![X][X]
+Luciano Resende | lresende | IBM | ![X][X]
+Mark Struberg | struberg | | ![X][X]
+Matt Benson | mbenson | Permanent General Assurance Corp | ![X][X] | ![X][X]
+Matthias Wessendorf | matzew | Kaazing | ![X][X]
+Mohammad Nour El-Din | mnour | Thebe Technology | ![X][X]
+Roman Stumm | romanstumm | Agimatec GmbH | ![X][X]
+Simone Tripodi | simonetripodi | | ![X][X]
+
+Apache BVal would like specifically to thank its incubation champion and
+mentor Kevan Miller. Thanks go also to mentors Luciano Resende, Matthias
+Wessendorf, and Niall Pemberton.
+
+[X]: /images/Fotolia_Check_16x16.png
Added: bval/cms-site/content/post-graduation-checklist.cwiki
URL: http://svn.apache.org/viewvc/bval/cms-site/content/post-graduation-checklist.cwiki?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/post-graduation-checklist.cwiki (added)
+++ bval/cms-site/content/post-graduation-checklist.cwiki Fri Mar 9 20:14:15 2012
@@ -0,0 +1,31 @@
+From [http://incubator.apache.org/guides/graduation.html#life-after-graduation]:
+
+Once appointed, the new Chair needs to:
+
+Notation:
+||Status||Icon||
+| Complete | (/) |
+| In-Progress | (!) |
+| Pending | (x) |
+
+||TASK||STATUS||
+| Subscribe to the board mailing list | (/) |
+| Subscribe to the infrastructure mailing list | (/) |
+| Ensure that they have been added to [the PMC chairs group (pmc-chairs) in LDAP|http://people.apache.org/committers-by-project.html#pmc-chairs]. | (/) |
+| Check out the foundation/officers folder from the private repository. Users with member or pmc-chairs karma can do this. | (/) |
+| Add yourself to the foundation/officers/affiliations.txt and the foundation/officers/irs-disclosures.txt files with the appropriate information. | (/) |
+
+Review appropriate documentation:
+| [PMC Chair Duties|http://www.apache.org/dev/pmc.html#chair] | (/) |
+| PMC [documentation|http://www.apache.org/dev/#pmc] | (/) |
+| Jakarta [Chair guide|http://wiki.apache.org/jakarta/RoleOfChair] | (/) |
+| Incubator [Chair guide|http://incubator.apache.org/guides/chair.html] | (/) |
+| Reporting [calendar|http://www.apache.org/foundation/board/calendar.html] | (/) |
+
+| Work out a reporting schedule with the [Board|http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board]. For the first three months after graduation this will be monthly. After that, the project should slot into a quarterly reporting schedule. Now is a good time to remove the project from the Incubator reporting schedule. | (/) |
+| Work with the [Apache Infrastructure team|http://www.apache.org/dev/index.html#infra] to set up the top level project infrastructure. The various infrastructure tasks that are required (see [check list|http://incubator.apache.org/guides/graduation.html#transfer]) should be consolidated into a single issue. This should be created in the category [TLP Admin|https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10410&sorter/order=DESC&sorter/field=priority&resolution=-1&component=10858]. See [https://issues.apache.org/jira/browse/INFRA-4446]. | (!) |
+| Add the new project to the foundation web site. Instructions for updating the web site are [here|http://www.apache.org/dev/infra-site.html]. | (x) |
+| Add the PMC chair details to the foundation web site Officer list at [http://www.apache.org/foundation/index.html] | (/) |
+| Add the new project's PMC chair to the foundation/officers/irs-disclosures.txt file. You will need a member to help with this task. *DUPLICATE* | (/) |
+| Ensure the PMC is added to the committee-info.txt file at https://svn.apache.org/repos/private/committers/board/committee-info.txt;
+There are 3 sections which need to be updated; see instructions in the file. You may need to get a member to help with this. | (/) |
\ No newline at end of file
Added: bval/cms-site/content/post-graduation-checklist.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/content/post-graduation-checklist.mdtext?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/post-graduation-checklist.mdtext (added)
+++ bval/cms-site/content/post-graduation-checklist.mdtext Fri Mar 9 20:14:15 2012
@@ -0,0 +1,67 @@
+Title: Post-graduation checklist
+From [http://incubator.apache.org/guides/graduation.html#life-after-graduation](http://incubator.apache.org/guides/graduation.html#life-after-graduation)
+:
+
+Once appointed, the new Chair needs to:
+
+Notation:
+<table>
+<tr><th>Status</th><th>Icon</th></tr>
+<tr><td> Complete </td><td> (/) </td></tr>
+<tr><td> In-Progress </td><td> (!) </td></tr>
+<tr><td> Pending </td><td> (x) </td></tr>
+</table>
+
+<table>
+<tr><th>TASK</th><th>STATUS</th></tr>
+<tr><td> Subscribe to the board mailing list </td><td> (/) </td></tr>
+<tr><td> Subscribe to the infrastructure mailing list </td><td> (/) </td></tr>
+<tr><td> Ensure that they have been added to [the PMC chairs group (pmc-chairs) in LDAP](http://people.apache.org/committers-by-project.html#pmc-chairs)
+. </td><td> (/) </td></tr>
+<tr><td> Check out the foundation/officers folder from the private repository.
+Users with member or pmc-chairs karma can do this. </td><td> (/) </td></tr>
+<tr><td> Add yourself to the foundation/officers/affiliations.txt and the
+foundation/officers/irs-disclosures.txt files with the appropriate
+information. </td><td> (/) </td></tr>
+</table>
+
+Review appropriate documentation:
+<table>
+<tr><td> [PMC Chair Duties](http://www.apache.org/dev/pmc.html#chair)
+ </td><td> (/) </td></tr>
+<tr><td> PMC [documentation](http://www.apache.org/dev/#pmc)
+ </td><td> (/) </td></tr>
+<tr><td> Jakarta [Chair guide](http://wiki.apache.org/jakarta/RoleOfChair)
+ </td><td> (/) </td></tr>
+<tr><td> Incubator [Chair guide](http://incubator.apache.org/guides/chair.html)
+ </td><td> (/) </td></tr>
+<tr><td> Reporting [calendar](http://www.apache.org/foundation/board/calendar.html)
+ </td><td> (/) </td></tr>
+</table>
+
+<table>
+<tr><td> Work out a reporting schedule with the [Board](http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board)
+. For the first three months after graduation this will be monthly. After
+that, the project should slot into a quarterly reporting schedule. Now is a
+good time to remove the project from the Incubator reporting schedule. </td><td>
+(/) </td></tr>
+<tr><td> Work with the [Apache Infrastructure team](http://www.apache.org/dev/index.html#infra)
+ to set up the top level project infrastructure. The various infrastructure
+tasks that are required (see [check list</td><td>http://incubator.apache.org/guides/graduation.html#transfer]
+) should be consolidated into a single issue. This should be created in the
+category [TLP Admin</td><td>https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10410&sorter/order=DESC&sorter/field=priority&resolution=-1&component=10858]
+. See [https://issues.apache.org/jira/browse/INFRA-4446]
+. </td><td> (!) </td></tr>
+<tr><td> Add the new project to the foundation web site. Instructions for updating
+the web site are [here](http://www.apache.org/dev/infra-site.html)
+. </td><td> (x) </td></tr>
+<tr><td> Add the PMC chair details to the foundation web site Officer list at [http://www.apache.org/foundation/index.html](http://www.apache.org/foundation/index.html)
+ </td><td> (/) </td></tr>
+<tr><td> Add the new project's PMC chair to the
+foundation/officers/irs-disclosures.txt file. You will need a member to
+help with this task. *DUPLICATE* </td><td> (/) </td></tr>
+<tr><td> Ensure the PMC is added to the committee-info.txt file at
+https://svn.apache.org/repos/private/committers/board/committee-info.txt;
+</tr>
+There are 3 sections which need to be updated; see instructions in the
+file. You may need to get a member to help with this. | (/) |
Added: bval/cms-site/content/privacy-policy.cwiki
URL: http://svn.apache.org/viewvc/bval/cms-site/content/privacy-policy.cwiki?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/privacy-policy.cwiki (added)
+++ bval/cms-site/content/privacy-policy.cwiki Fri Mar 9 20:14:15 2012
@@ -0,0 +1,22 @@
+All materials provided on the Apache BVal website Copyright © 2010-2012, The Apache Software Foundation and Licensed under [AL v2.0|http://www.apache.org/licenses/LICENSE-2.0].
+
+Privacy Policy - Last Updated: April 1, 2010
+
+Information about your use of this website is collected using [server access logs|http://people.apache.org/~vgritsenko/stats/] and a tracking cookie. The collected information consists of the following:
+* The IP address from which you access the website;
+* The type of browser and operating system you use to access our site;
+* The date and time you access our site;
+* The pages you visit; and
+* The addresses of pages from where you followed a link to our site.
+
+Part of this information is gathered using a tracking cookie set by the [Google Analytics|http://www.google.com/analytics/] service and handled by Google as described in their [privacy policy|http://www.google.com/privacy.html]. See your browser documentation for instructions on how to disable the cookie if you prefer not to share this data with Google.
+
+We use the gathered information to help us make our site more useful to visitors and to better understand how and when our site is used. We do not track or collect personally identifiable information or associate gathered data with any personally identifying information from other sources.
+
+By using this website, you consent to the collection of this data in the manner and for the purpose described above.
+
+Occasionally, at our discretion, we may include links to other third party content or services on our website. These third party sites have separate and independent privacy policies and therefore we have no responsibility or liability for the content and activities of these linked sites.
+
+If we make changes to our privacy policy, we will send a notification to our mailing lists <us...@bval.apache.org> and <de...@bval.apache.org> along with updating the "Last Updated" date at the top of this page.
+
+If there are any questions regarding this privacy policy, you can contact us on the following mailing list <pr...@bval.apache.org>.
Added: bval/cms-site/content/privacy-policy.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/content/privacy-policy.mdtext?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/privacy-policy.mdtext (added)
+++ bval/cms-site/content/privacy-policy.mdtext Fri Mar 9 20:14:15 2012
@@ -0,0 +1,40 @@
+Title: Privacy Policy
+All materials provided on the Apache BVal website Copyright © 2010-2012,
+The Apache Software Foundation and Licensed under [AL v2.0](http://www.apache.org/licenses/LICENSE-2.0).
+
+Privacy Policy - Last Updated: April 1, 2010
+
+Information about your use of this website is collected using [server access logs](http://people.apache.org/~vgritsenko/stats/)
+ and a tracking cookie. The collected information consists of the
+following:
+
+* The IP address from which you access the website;
+* The type of browser and operating system you use to access our site;
+* The date and time you access our site;
+* The pages you visit; and
+* The addresses of pages from where you followed a link to our site.
+
+Part of this information is gathered using a tracking cookie set by the [Google Analytics](http://www.google.com/analytics/)
+ service and handled by Google as described in their [privacy policy|http://www.google.com/privacy.html]
+. See your browser documentation for instructions on how to disable the
+cookie if you prefer not to share this data with Google.
+
+We use the gathered information to help us make our site more useful to
+visitors and to better understand how and when our site is used. We do not
+track or collect personally identifiable information or associate gathered
+data with any personally identifying information from other sources.
+
+By using this website, you consent to the collection of this data in the
+manner and for the purpose described above.
+
+Occasionally, at our discretion, we may include links to other third party
+content or services on our website. These third party sites have separate
+and independent privacy policies and therefore we have no responsibility or
+liability for the content and activities of these linked sites.
+
+If we make changes to our privacy policy, we will send a notification to
+our mailing lists <us...@bval.apache.org> and <de...@bval.apache.org> along
+with updating the "Last Updated" date at the top of this page.
+
+If there are any questions regarding this privacy policy, you can contact
+us on the following mailing list <pr...@bval.apache.org>.
Added: bval/cms-site/content/privacy-policy.mdtext.bak
URL: http://svn.apache.org/viewvc/bval/cms-site/content/privacy-policy.mdtext.bak?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/privacy-policy.mdtext.bak (added)
+++ bval/cms-site/content/privacy-policy.mdtext.bak Fri Mar 9 20:14:15 2012
@@ -0,0 +1,39 @@
+All materials provided on the Apache BVal website Copyright © 2010-2012,
+The Apache Software Foundation and Licensed under [AL v2.0](http://www.apache.org/licenses/LICENSE-2.0).
+
+Privacy Policy - Last Updated: April 1, 2010
+
+Information about your use of this website is collected using [server access logs](http://people.apache.org/~vgritsenko/stats/)
+ and a tracking cookie. The collected information consists of the
+following:
+
+* The IP address from which you access the website;
+* The type of browser and operating system you use to access our site;
+* The date and time you access our site;
+* The pages you visit; and
+* The addresses of pages from where you followed a link to our site.
+
+Part of this information is gathered using a tracking cookie set by the [Google Analytics](http://www.google.com/analytics/)
+ service and handled by Google as described in their [privacy policy|http://www.google.com/privacy.html]
+. See your browser documentation for instructions on how to disable the
+cookie if you prefer not to share this data with Google.
+
+We use the gathered information to help us make our site more useful to
+visitors and to better understand how and when our site is used. We do not
+track or collect personally identifiable information or associate gathered
+data with any personally identifying information from other sources.
+
+By using this website, you consent to the collection of this data in the
+manner and for the purpose described above.
+
+Occasionally, at our discretion, we may include links to other third party
+content or services on our website. These third party sites have separate
+and independent privacy policies and therefore we have no responsibility or
+liability for the content and activities of these linked sites.
+
+If we make changes to our privacy policy, we will send a notification to
+our mailing lists <us...@bval.apache.org> and <de...@bval.apache.org> along
+with updating the "Last Updated" date at the top of this page.
+
+If there are any questions regarding this privacy policy, you can contact
+us on the following mailing list <pr...@bval.apache.org>.
Added: bval/cms-site/content/release-management.cwiki
URL: http://svn.apache.org/viewvc/bval/cms-site/content/release-management.cwiki?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/release-management.cwiki (added)
+++ bval/cms-site/content/release-management.cwiki Fri Mar 9 20:14:15 2012
@@ -0,0 +1,12 @@
+We'll be using the Apache Nexus repository (repository.apache.org) for releasing SNAPSHOT and release artifacts, which uses the same LDAP groups as SVN to control who can publish artifacts using groupId=org.apache.bval.
+
+To familiarize yourself with the notions and requirements for releasing artifacts, please checkout the [Apache Release FAQ|http://www.apache.org/dev/release.html].
+
+As BVal is a graduated Incubator project, the [Incubator Release Guidelines|http://incubator.apache.org/guides/releasemanagement.html] may be of interest.
+
+
+h3. Apache BVal Release Guidelines
+{children}
+
+\\
+
Added: bval/cms-site/content/release-management.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/content/release-management.mdtext?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/release-management.mdtext (added)
+++ bval/cms-site/content/release-management.mdtext Fri Mar 9 20:14:15 2012
@@ -0,0 +1,18 @@
+Title: Release Management
+We'll be using the [Apache Nexus repository](http://repository.apache.org) for
+releasing `SNAPSHOT` and release artifacts, which uses the same LDAP groups
+as SVN to control who can publish artifacts using `groupId=org.apache.bval`.
+
+To familiarize yourself with the notions and requirements for releasing
+artifacts, please check out the
+[Apache Release FAQ](http://www.apache.org/dev/release.html).
+
+As BVal is a graduated Incubator project, the
+[Incubator Release Guidelines](http://incubator.apache.org/guides/releasemanagement.html)
+may be of interest.
+
+<a name="ReleaseManagement-ApacheBValReleaseGuidelines"></a>
+### Apache BVal Release Guidelines
+
+* [Release Setup](/release-setup.html)
+* [Release Process](/release-process.html)
Added: bval/cms-site/content/release-process.cwiki
URL: http://svn.apache.org/viewvc/bval/cms-site/content/release-process.cwiki?rev=1299018&view=auto
==============================================================================
--- bval/cms-site/content/release-process.cwiki (added)
+++ bval/cms-site/content/release-process.cwiki Fri Mar 9 20:14:15 2012
@@ -0,0 +1,262 @@
+We'll be using the Apache Nexus repository (repository.apache.org) for releasing SNAPSHOT and release artifacts. More details on releasing artifacts and using Nexus can be found on the Maven website at - [http://maven.apache.org/developers/release/apache-release.html]
+
+h3. Release Steps
+
+# Environment setup for releasing artifacts (same for SNAPSHOTs and releases) -
+## Increase the default Java heap available to Maven (required for Java SE 6)
+{code:none}
+export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"
+{code}
+## Use the latest Sun 1.6.0 JDK
+## Use Maven 2.2.1 or later (2.2.1 is required for release signing fixes)
+## Make sure the [Release Setup] steps have been performed.
+# Prepare the source for release:
+## Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly. Also, transition any Resolved issues to the Closed state.
+## Update the text files in a working copy of the project root -
+### Update the CHANGES.txt based on the Text release reports from JIRA.
+### Review and update README.txt if needed.
+### Commit any changes back to svn -
+{code:none}
+$ svn commit -m "updating files for release"
+{code}
+## Stage any Roadmap or Release landing pages on the wiki.
+## Use "mvn rat:check" to verify the source has the required headers before trying to release.
+## Perform a full build and deploy the SNAPSHOT artifacts
+{code:none}
+$ mvn clean deploy -Papache-release
+{code}
+## Run the [JSR303 TCK] to verify the latest code passes.
+## Inspect the files in your local target directories to ensure:
+### All jars and zips include: LICENSE, NOTICE, DISCLAIMER files
+### The NOTICE files cover all third-party included files (like XSD schemas)
+### The LICENSE files include any third-party licenses (none at this time)
+### All jars/zips/poms have .asc (PGP signature) and md5 files
+# For new major releases (like 1.0.0 to 1.1.0)
+## Create a sub-branch from which to make the release. Releasing from a branch will allow any cosmetic changes that need to be made for the release to be approved to be done without preventing other more disruptive advances in the trunk from potentially causing problems with the release. It also provides a future maintenance branch (like 1.0.x.) A branch can be made by running: \\
+{code:none}
+$ mvn release:branch -DbranchName=1.0.x
+{code}
+# Checkout a clean copy of the trunk/branch to release using command line svn.
+## Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws off the rat:check processing. \\
+{code:none}
+$ svn checkout https://svn.apache.org/repos/asf/bval/trunk/ 1.0-rc1/
+{code}
+# Do a dry run of the release:prepare step.
+## The dry run will not commit any changes back to SVN and gives you the opportunity to verify that the release process will complete as expected. You will be prompted for the following information :
+### Release version - take the default - (default 1.0)
+### SCM release tag - *DO NOT TAKE THE DEFAULT - (default bval-1.0): : 1.0
+### New development version - take the default - (default 1.0.1-SNAPSHOT)
+### _optional_ if you have not specified a GPG passphrase in settings.xml you will be prompted for it.
+{code:none}
+$ mvn -Papache-release release:prepare -DdryRun=true
+<snip>
+[INFO] Working directory: /Users/drwoods/bval/1.0-rc1
+[INFO] Checking dependencies and plugins for snapshots ...
+What is the release version for "Apache BVal :: bval-parent (Parent POM)"? (org.apache.bval:bval-parent) 1.0: :
+What is SCM release tag or label for "Apache BVal :: bval-parent (Parent POM)"? (org.apache.bval:bval-parent) bval-parent-1.0: : 1.0
+What is the new development version for "Apache BVal :: bval-parent (Parent POM)"? (org.apache.bval:bval-parent) 1.0.1-SNAPSHOT: :
+[INFO] Transforming 'Apache BVal :: bval-parent (Parent POM)'...
+<snip>
+{code}
+{note}
+If you cancel a release:prepare before it updates the pom.xml versions, then use the *release:clean* goal to just remove the extra files that were created.
+{note}
+# Verify that the release process completed as expected
+## The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number.
+## If other formatting changes have been made you should review the changes and then commit them -
+{code:none}
+$ svn commit -m "fixing formatting for release"
+{code}
+## Assuming the .tag files look OK you may proceed and do any other validation you feel necessary. The following list may be helpful
+### Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.
+### verify signatures [#Verifying release signatures]
+### if you have access to the TCK, run it [JSR303 TCK]
+## Once any failures or required updates have been committed to svn, rollback the release prepare files -
+{code:none}
+$ mvn -Papache-release release:rollback
+{code}
+# Prepare the release
+## Run the "release:prepare" step for real this time. You'll be prompted for the same version information and optionally your GPG passphrase again.
+{note}Different arguments and steps are required as there are problems with the maven-jar-plugin and maven-release-plugin when using the test-jar goal. See [http://jira.codehaus.org/browse/MJAR-68] and [http://jira.codehaus.org/browse/MRELEASE-285].
+{note}
+{code:none}
+$ mvn release:prepare -Papache-release -DskipTests=true -DpreparationGoals="clean install"
+{code}
+# Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.
+{code:none}
+cd ..
+tar -czf 1.0-rc1.tar.gz 1.0-rc1/
+cd 1.0-rc1
+{code}
+# Perform the release
+## This step will create a maven staging repository and site for use in testing and voting. You will be prompted for your repository.apache.org and people.apache.org password several times if you have not added server profiles to your settings.xml. See [Release Setup] for more information.
+{code:none}
+$ mvn release:perform -Papache-release -Duser.name=<your_apache_uid>
+{code}
+{note} If your local OS userid doesn't match your Apache userid, then you'll have to also override the value provided by the OS to Maven for the site-deploy step to work. This is known to work for Linux, but not for Mac and unknown for Windows.
+{note}
+## The maven-release-plugin is configured with goals "deploy site site:deploy" and will deploy the site files to a staging-site directory on people.apache.org.
+# Verify the release artifacts
+## Verify the HTML links in staging-site/index.html are correct
+## Verify the staged artifacts in the nexus repo
+### https://repository.apache.org/index.html
+### Enterprise --> Staging
+### Staging tab --> Name column --> org.apache.bval
+### Navigate through the artifact tree and make sure that all javadoc, sources, tests, jars, ... have .asc (GPG signature) and .md5 files. See [http://people.apache.org/~henkp/repo/faq.html] and [http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig]
+## Close the nexus staging repo
+### https://repository.apache.org/index.html
+### Enterprise --> Staging
+### Staging tab --> Name column --> org.apache.bval
+### Right click on the open staging repo (org.apache.bval-XXX) and select Close.
+# Put the release candidate up for a vote
+## Create a VOTE email thread on bval-dev@ to record votes as replies, like -
+{code:none}
+To: bval-dev@
+Subject: [VOTE] Apache BVal 1.0 Release Candidate
+
+I've created a 1.0 release candidate, with the following artifacts up for a vote:
+
+SVN source tag (r950702):
+https://svn.apache.org/repos/asf/bval/tags/1.0/
+
+Maven staging repo:
+https://repository.apache.org/content/repositories/orgapachebval-020/
+
+Source release:
+https://repository.apache.org/content/repositories/orgapachebval-020/org/apache/bval/bval-parent/1.0/bval-parent-1.0-source-release.zip
+
+Javadoc staging site:
+http://people.apache.org/~mbenson/bval/1.0/staging-site/apidocs/
+
+PGP release keys (signed using D018E6B1):
+https://svn.apache.org/repos/asf/bval/KEYS
+
+
+Vote will be open for 72 hours.
+
+[ ] +1 approve
+[ ] +0 no opinion
+[ ] -1 disapprove (and reason why)
+
+{code}
+## Create a DISCUSS email thread on bval-dev@ for any vote questions, like -
+{code:none}
+To: bval-dev@
+Subject: [DISCUSS] Apache BVal 1.0 Release Candidate
+
+Discussion thread for vote on 1.0 release candidate, with SVN source tag (r999999).
+
+For more information on the release process, checkout -
+http://www.apache.org/dev/release.html
+
+Some of the things to check before voting are:
+- does "mvn apache-rat:check" pass on the source
+- can you build the contents of source-release.zip and svn tag
+- do all of the staged jars/zips contain the required LICENSE, NOTICE
+and DISCLAIMER files
+- are all of the staged jars signed and the signature verifiable
+- is the signing key in the project's KEYS file and on a public server
+- does the release pass the TCK
+
+{code}
+## Perform a review of the release and cast your vote. See the following for more details on Apache releases -
+### [http://www.apache.org/dev/release.html]
+## A -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea to rollback the release if a -1 vote is received. See - [#Recovering from a vetoed release]
+## After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes, then post the results to the vote thread by -
+### reply to the initial email and prepend to the original subject -
+{code:none}[RESULT]{code}
+### Include a list of everyone who voted +1, 0 or -1.
+
+# Finalizing a release
+## Promote the staged nexus artifacts -
+### https://repository.apache.org/index.html
+### Enterprise --> Staging
+### Staging tab --> Name column --> org.apache.bval
+### Right click on the closed staging repo (org.apache.bval-XXX) and select Promote.
+## Copy the staged site over to our website area
+{code:none}
+$ ssh ${user.name}@people.apache.org
+$ mkdir /www/bval.apache.org/${project.version}
+$ cp -R ~/public_html/bval/${project.version}/staging-site/* /www/bval.apache.org/${project.version}
+# Make sure all the copied files have g+rw set and only o+r set
+$ cd /www/bval.apache.org
+$ find . -user ${user.name} -type f | xargs chmod 664
+$ find . -user ${user.name} -type d | xargs chmod 775
+{code}
+## Update the *Documentation* wiki page to point to the new apidocs
+{code:none}
+http://bval.apache.org/${project.version}/apidocs/
+{code}
+## Copy the distribution artifacts over to the distribution area
+{code:none}
+$ ssh ${user.name}@people.apache.org
+$ mkdir /www/www.apache.org/dist/bval/${project.version}
+$ cd /www/www.apache.org/dist/bval/${project.version}
+$ wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/${project.version}/bval-parent-${project.version}-source-release.zip
+$ wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/${project.version}/bval-parent-${project.version}-source-release.zip.asc
+$ wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/${project.version}/bval-parent-${project.version}-source-release.zip.md5
+$ wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/${project.version}/bval-parent-${project.version}-source-release.zip.sha1
+# Make sure all the copied files have g+rw set and only o+r set
+$ find . -user ${user.name} -type f | xargs chmod 664
+$ find . -user ${user.name} -type d | xargs chmod 775
+# Note: All of the artifacts are in the maven repos, but we may create an assembly to publish in future releases
+{code}
+## Update the *Downloads* wiki page to point to the new release artifacts
+{code:none}
+http://www.apache.org/dyn/closer.cgi/bval/${project.version}/
+http://repo1.maven.org/maven2/org/apache/bval/${artifactId}/${project.version}/
+{code}
+## Update the [JIRA versions | https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12311080] page to mark the version as "released", and set the date to the date that the release was approved. You may also need to make a new release entry for the next release.
+# Announcing the release
+## After the mirrors have had time to update (24 hours to be on the safe side) update the wiki with pointers to the new release
+## Make a [news announcement|http://cwiki.apache.org/confluence/pages/createblogpost.action?spaceKey=BeanValidation] on the BVal wiki.
+## Make an announcement about the release on the [mailto:users@bval.apache.org], [mailto:dev@bval.apache.org], and [mailto:announce@apache.org] list as per [the Apache Announcement Mailing Lists page|http://www.apache.org/foundation/mailinglists.html#foundation-announce])
+
+\\
+
+h3. Recovering from a vetoed release
+# Reply to the initial vote email and prepend to the original subject -
+{code:none}[CANCELED]{code}
+# Rollback the version upgrades in trunk by either -
+## Restore the 0.1-rc1.tar.gz and run
+{code:none}
+$ mvn -Papache-release release:rollback
+{code}
+## Manually revert the versions in trunk to the prior version and commit
+# Delete the svn tag created by the release:perform step -
+{code:none}
+$ svn del https://svn.apache.org/repos/asf/bval/tags/1.0 -m "deleting tag from rolled back release"
+{code}
+# Drop the nexus staging repo
+## https://repository.apache.org/index.html
+## Enterprise --> Staging
+## Staging tab --> Name column --> org.apache.bval
+## Right click on the closed staging repo (org.apache.bval-XXX) and select Drop.
+# Remote the staged site
+{code:none}
+$ ssh ${user.name}@people.apache.org
+$ cd ~/public_html/bval
+$ rm -fr ${project.version}
+{code}
+# Make the required updates that caused the vote to be canceled
+# Spin another release candidate!
+
+\\
+
+h3. Verifying release signatures
+
+On unix platforms the following command can be executed -
+{code:none}
+for file in `find . -type f -iname '*.asc'`
+do
+ gpg --verify ${file}
+done
+{code}
+
+You'll need to look at the output to ensure it contains only good signatures -
+{code:none}
+gpg: Good signature from ...
+gpg: Signature made ...
+{code}
+
+\\