Return-Path: X-Original-To: apmail-bval-commits-archive@www.apache.org Delivered-To: apmail-bval-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B0CD29CCD for ; Sat, 10 Mar 2012 22:52:00 +0000 (UTC) Received: (qmail 13272 invoked by uid 500); 10 Mar 2012 22:52:00 -0000 Delivered-To: apmail-bval-commits-archive@bval.apache.org Received: (qmail 13251 invoked by uid 500); 10 Mar 2012 22:52:00 -0000 Mailing-List: contact commits-help@bval.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bval-dev@bval.apache.org Delivered-To: mailing list commits@bval.apache.org Received: (qmail 13243 invoked by uid 99); 10 Mar 2012 22:52:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Mar 2012 22:52:00 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Mar 2012 22:51:37 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id E8CA12388C1F for ; Sat, 10 Mar 2012 22:51:14 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r808152 [5/7] - in /websites/staging/bval/trunk/content: ./ board-reports/ coding/ images/ resources/ Date: Sat, 10 Mar 2012 22:51:11 -0000 To: commits@bval.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120310225114.E8CA12388C1F@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Added: websites/staging/bval/trunk/content/obtaining-a-validator.cwiki ============================================================================== --- websites/staging/bval/trunk/content/obtaining-a-validator.cwiki (added) +++ websites/staging/bval/trunk/content/obtaining-a-validator.cwiki Sat Mar 10 22:51:09 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} + + + + +{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} + + org.apache.bval + bval-guice + 0.3-incubating + +{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 { + + 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: websites/staging/bval/trunk/content/obtaining-a-validator.html ============================================================================== --- websites/staging/bval/trunk/content/obtaining-a-validator.html (added) +++ websites/staging/bval/trunk/content/obtaining-a-validator.html Sat Mar 10 22:51:09 2012 @@ -0,0 +1,412 @@ + + + + + + + + + + + + + + + + + + + + + + + Apache BVal + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
   
   +
+ +
+ + 		  
  + + + + + +
+
+
+
+
+ +

+

Overview

+ +

+

Community

+ +

+

Development

+ +

+

Sponsorship

+ +

+ +

+
+ + + + + + +
+

+ +
+
+
+
+ 		+ +

To obtain a Validator, you must first create a ValidatorFactory. If there +is only one Bean Validation implementation in your classpath, you can use:

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

+
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 Validators from it:

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

+
MyValidatorFactory.SINGLE_INSTANCE.getValidator()
+
+ + +

+

Using The Spring Framework

+

If you are using Spring, you can easily inject Validators into your beans. +Simply configure the factory in your ApplicationContext by adding:

+
<!-- 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 Validators and the ValidatorFactory into +your beans.

+

+

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

+
<dependency>
+  <groupId>org.apache.bval</groupId>
+  <artifactId>bval-guice</artifactId>
+  <version>0.3-incubating</version>
+</dependency>
+
+ + +

Let's have a look at the features:

+

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

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

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

+

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

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

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

+

Using CDI

+

Bean Validation integration with CDI is provided by:

+
+ +
+ 		 
   + +   
  + +  
   
+ + Added: websites/staging/bval/trunk/content/overview.cwiki ============================================================================== --- websites/staging/bval/trunk/content/overview.cwiki (added) +++ websites/staging/bval/trunk/content/overview.cwiki Sat Mar 10 22:51:09 2012 @@ -0,0 +1 @@ +{children} \ No newline at end of file Added: websites/staging/bval/trunk/content/overview.html ============================================================================== --- websites/staging/bval/trunk/content/overview.html (added) +++ websites/staging/bval/trunk/content/overview.html Sat Mar 10 22:51:09 2012 @@ -0,0 +1,211 @@ + + + + + + + + + + + + + + + + + + + + + + + Apache BVal + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
   
   +
+ +
+ + 		  
  + + + + + +
+
+
+
+
+ +

+

Overview

+ +

+

Community

+ +

+

Development

+ +

+

Sponsorship

+ +

+ +

+
+ + + + + + +
+

+ +
+
+
+
+ 		+ +

{children}

+ +
+ 		 
   + +   
  + +  
   
+ + Added: websites/staging/bval/trunk/content/people.cwiki ============================================================================== --- websites/staging/bval/trunk/content/people.cwiki (added) +++ websites/staging/bval/trunk/content/people.cwiki Sat Mar 10 22:51:09 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: websites/staging/bval/trunk/content/people.html ============================================================================== --- websites/staging/bval/trunk/content/people.html (added) +++ websites/staging/bval/trunk/content/people.html Sat Mar 10 22:51:09 2012 @@ -0,0 +1,325 @@ + + + + + + + + + + + + + + + + + + + + + + + Apache BVal + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
   
   +
+ +
+ + 		  
  + + + + + +
+
+
+
+
+ +

+

Overview

+ +

+

Community

+ +

+

Development

+ +

+

Sponsorship

+ +

+ +

+
+ + + + + + +
+

+ +
+
+
+
+ 		+ +

This is a list of the people involved in Apache BVal and their roles.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameIdOrganizationPMC MemberPMC chair
Albert Leeallee8285X
Carlos VaracarlosvaraAmazonX
David JencksdjencksIBMX
Donald WoodsdwoodsIBMX
Gerhard PetracekgpetracekIRIAN Solutions GmbHX
Jeremy BauerjrbauerIBMX
Kevan MillerkevanIBMX
Luciano ResendelresendeIBMX
Mark StrubergstrubergX
Matt BensonmbensonPermanent General Assurance CorpXX
Matthias WessendorfmatzewKaazingX
Mohammad Nour El-DinmnourThebe TechnologyX
Roman StummromanstummAgimatec GmbHX
Simone TripodisimonetripodiX
+

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.

+ +
+ 		 
   + +   
  + +  
   
+ + Added: websites/staging/bval/trunk/content/post-graduation-checklist.cwiki ============================================================================== --- websites/staging/bval/trunk/content/post-graduation-checklist.cwiki (added) +++ websites/staging/bval/trunk/content/post-graduation-checklist.cwiki Sat Mar 10 22:51:09 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: websites/staging/bval/trunk/content/post-graduation-checklist.html ============================================================================== --- websites/staging/bval/trunk/content/post-graduation-checklist.html (added) +++ websites/staging/bval/trunk/content/post-graduation-checklist.html Sat Mar 10 22:51:09 2012 @@ -0,0 +1,272 @@ + + + + + + + + + + + + + + + + + + + + + + + Apache BVal + + + + + + + + + + + + + + + + + + + +
   
   +
+ +
+ + 		  
  + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+
+ +

+

Overview

+ +

+

Community

+ +

+

Development

+ +

+

Sponsorship

+ +

+ +

+
+ + + + + + +
+

+ +
+
+
+
+ 		+ +

From http://incubator.apache.org/guides/graduation.html#life-after-graduation +:

+

Once appointed, the new Chair needs to:

+

Notation: + + + + + +
StatusIcon
Complete (/)
In-Progress (!)
Pending (x)

+ + + + + + + +
TASKSTATUS
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 + (/)
PMC documentation + (/)
Jakarta Chair guide + (/)
Incubator Chair guide + (/)
Reporting calendar + (/)

+ + + + + + + +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. | (/) | + + + +
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 listhttp://incubator.apache.org/guides/graduation.html#transfer] +) should be consolidated into a single issue. This should be created in the +category [TLP Adminhttps://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](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; +
+
 
   + +   
  + +  
   
+ + Added: websites/staging/bval/trunk/content/privacy-policy.cwiki ============================================================================== --- websites/staging/bval/trunk/content/privacy-policy.cwiki (added) +++ websites/staging/bval/trunk/content/privacy-policy.cwiki Sat Mar 10 22:51:09 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 and 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 . Added: websites/staging/bval/trunk/content/privacy-policy.html ============================================================================== --- websites/staging/bval/trunk/content/privacy-policy.html (added) +++ websites/staging/bval/trunk/content/privacy-policy.html Sat Mar 10 22:51:09 2012 @@ -0,0 +1,242 @@ + + + + + + + + + + + + + + + + + + + + + + + Apache BVal + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
   
   +
+ +
+ + 		  
  + + + + + +
+
+
+
+
+ +

+

Overview

+ +

+

Community

+ +

+

Development

+ +

+

Sponsorship

+ +

+ +

+
+ + + + + + +
+

+ +
+
+
+
+ 		+ +

All materials provided on the Apache BVal website Copyright © 2010-2012, +The Apache Software Foundation and Licensed under AL v2.0.

+

Privacy Policy - Last Updated: April 1, 2010

+

Information about your use of this website is collected using server access logs + 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 + 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 users@bval.apache.org and dev@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 private@bval.apache.org.

+ +
+ 		 
   + +   
  + +  
   
+ + Added: websites/staging/bval/trunk/content/privacy-policy.mdtext.bak ============================================================================== --- websites/staging/bval/trunk/content/privacy-policy.mdtext.bak (added) +++ websites/staging/bval/trunk/content/privacy-policy.mdtext.bak Sat Mar 10 22:51:09 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 and 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 . Added: websites/staging/bval/trunk/content/release-management.cwiki ============================================================================== --- websites/staging/bval/trunk/content/release-management.cwiki (added) +++ websites/staging/bval/trunk/content/release-management.cwiki Sat Mar 10 22:51:09 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} + +\\ +