Re: [DISCUSS] beanval module name

works for me, so waiting for the vote *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/6

Re: [DISCUSS] beanval module name

we won't get a full agreement on that. we just need a majority for one abbreviation. if you don't agree (for whatever reason) with "bv" (which was coined by the eg and is used since years), you are welcome to vote for a different abbreviation. regards, gerhard 2013/6/16 Romain Manni-Bucau > c

Re: [DISCUSS] beanval module name

codi is not that used, and not sure bv is explicit enough in all languages. hibernate uses "validator", other can use jsr330/jsr349. Since this module can be an in between 330 and 349 maybe using jsr330 is good but IMO has the same drawback as "bv". If you don't follow specs and/or dev them you do

Re: [DISCUSS] beanval module name

we never had an issue with that in codi where we use "bv" since 2010. regards, gerhard 2013/6/16 Romain Manni-Bucau > even when speaking? > > Then the point is who should understand the name, the EG or users. > > *Romain Manni-Bucau* > *Twitter: @rmannibucau *

Re: [DISCUSS] beanval module name

even when speaking? Then the point is who should understand the name, the EG or users. *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*

Re: [DISCUSS] beanval module name

we (= bv-eg) ~always used "bv". it's even used in the bv-spec. document. regards, gerhard 2013/6/16 Romain Manni-Bucau > whatever the list is IMO, the point was already mentionned: how many times > did you use "bv" to say bean validation? You never say "Java Persistence > API" but always jpa,

Re: [DISCUSS] beanval module name

whatever the list is IMO, the point was already mentionned: how many times did you use "bv" to say bean validation? You never say "Java Persistence API" but always jpa, for bval that's the opposite IMO. I commonly see bval or beanvalidation but not others. *Romain Manni-Bucau* *Twitter: @rmannibu

Re: [DISCUSS] beanval module name

Gerhard, They may use [bv-dev] as a prefix, but the mailing list name is beanvalidation-dev. On Sun, Jun 16, 2013 at 10:11 AM, Gerhard Petracek < gerhard.petra...@gmail.com> wrote: > hi john, > > please check e.g. the official eg/dev list [1]. > the subject of mails starts with "[bv-dev]" > > r

Re: [DISCUSS] beanval module name

hi john, please check e.g. the official eg/dev list [1]. the subject of mails starts with "[bv-dev]" regards, gerhard [1] http://lists.jboss.org/pipermail/beanvalidation-dev/ 2013/6/16 John D. Ament > gerhard/thomas > > The problem I have with "bv" is that no one refers to BeanValidation as

Re: [DISCUSS] beanval module name

gerhard/thomas The problem I have with "bv" is that no one refers to BeanValidation as bv (in fact, Bean Validation is the shortened form of JavaBeans Validation). Doing a quick google search on bv shows me some STDs. Since google is typically stalking me and knows I ask lots of programming ques

Re: [DISCUSS] beanval module name

hi john, in codi we used bv1 (like jpa1, jsf12, jsf20,...). if we don't plan to support multiple versions with separated modules, i tend to like just "bv" (since we use "jpa" and "jsf" for the modules of the corresponding specs). regards, gerhard 2013/6/16 Romain Manni-Bucau > As a short nam

Re: [DISCUSS] beanval module name

+1 for bv (similiar to jpa, jsf, ...) 2013/6/16 Romain Manni-Bucau > As a short name bval is fine but maybe too close of apache impl. So id use > bean-validation. Being explicit is good when naming things > Le 16 juin 2013 15:25, "John D. Ament" a écrit : > > > Hi all > > > > One of the comme

Re: [DISCUSS] beanval module name

As a short name bval is fine but maybe too close of apache impl. So id use bean-validation. Being explicit is good when naming things Le 16 juin 2013 15:25, "John D. Ament" a écrit : > Hi all > > One of the comments in the introduction of a Bean Validation module is that > the name I gave it isn'

[DISCUSS] beanval module name

Hi all One of the comments in the introduction of a Bean Validation module is that the name I gave it isn't descriptive/useful. I chose the name "beanval" since it was a shortened version of "Bean Validation" that could easily be read via maven. To me, it's descriptive of being related to JSR303