bval-extras or bval-validator sounds good. I'd try the following mappings: org/apache/commons/validator/*Validator -> org.apache.bval.extras.constraints.*Validator
org/apache/commons/validator/routines/*Validator -> org.apache.bval.extras.constraints.routines.*Validator Looking at bval-jsr303, we currently have our constraints under org.apache.bval.constraints, which we should probably change over to org.apache.bval.jsr303.constraints to really denote these are only the spec required ones. -Donald On 12/7/10 3:55 AM, Simone Tripodi wrote: > Hi Donald, > thanks for your feedback, what about adding a new module 'bval-extras' > where putting all non-JSR303 constraints? > Thanks in advance, have a nice day, > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > > > On Tue, Dec 7, 2010 at 12:58 AM, Donald Woods <[email protected]> wrote: >> Sounds like a good idea, but we need to somehow distinguish between the >> JSR required constraints and any extras we supply. So, any non-JSR >> required constraints would not go into the bval-jsr303 module, but >> should go somewhere else (don't have a good suggestion right now.....) >> >> >> -Donald >> >> >> On 12/2/10 9:13 AM, Simone Tripodi wrote: >>> Hi all guys, >>> I think it could be good and I'd like to propose to add/migrate the >>> existing commons-validator routines[1] into our constraints[2] >>> package, what do you think? >>> Many thanks in advance, >>> Simo >>> >>> [1] >>> http://svn.apache.org/viewvc/commons/proper/validator/trunk/src/main/java/org/apache/commons/validator/routines/ >>> [2] >>> https://svn.apache.org/repos/asf/incubator/bval/trunk/bval-jsr303/src/main/java/org/apache/bval/constraints/ >>> >>> >>> http://people.apache.org/~simonetripodi/ >>> http://www.99soft.org/ >>> >> >
