<div dir="ltr">Sounds great.<div><br></div><div>Regards,</div><div>Michael</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 16, 2017 at 8:33 AM, Gunnar Morling <span dir="ltr"><<a href="mailto:gunnar@hibernate.org" target="_blank">gunnar@hibernate.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've been discussing the issue of the module name a bit with Emmanuel<br>
and we concluded that a non-binding recommendation in an appendix to<br>
the BV 2.0 spec should be alright. I've filed PR<br>
<a href="https://github.com/beanvalidation/beanvalidation-spec/pull/174" rel="noreferrer" target="_blank">https://github.com/<wbr>beanvalidation/beanvalidation-<wbr>spec/pull/174</a> for it,<br>
saying:<br>
<br>
"While not specified by this specification, Bean Validation<br>
providers are encouraged to use the module name `java.validation`<br>
in case they provide the Bean Validation API as a module for the Java<br>
Platform Module System (as defined by JSR 376).<br>
A mandatory module name - which may be `java.validation` or another<br>
one - will be defined in a future revision of this specification."<br>
<br>
This leaves the door open for choosing another value - and making it<br>
mandatory - down the road, while letting 2.0 providers converge on one<br>
non-officially sanctioned name for the time being (which is needed for<br>
the migration between providers).<br>
<span class="HOEnZb"><font color="#888888"><br>
--Gunnar<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
2017-05-09 18:50 GMT+02:00 Michael Nascimento <<a href="mailto:misterm@gmail.com">misterm@gmail.com</a>>:<br>
> In the JPA mailing list, Bill Shannon and Linda were saying specs shouldn't<br>
> mention anything about modules at this point. Some suggested this could be<br>
> done at the next MR. It's better to align with them then.<br>
><br>
> Regards,<br>
> Michael<br>
><br>
> On Tue, May 9, 2017 at 10:52 AM, Gunnar Morling <<a href="mailto:gunnar@hibernate.org">gunnar@hibernate.org</a>><br>
> wrote:<br>
>><br>
>> So "java.validation" should work (as a recommendation for now).<br>
>><br>
>> But I've learned that Oracle-led JSRs (e.g. JAX-RS 2.1) don't mention<br>
>> anything in the spec (JAX-RS reference API just has a module-info.java<br>
>> with a name they chose). We could do the same, and just have that<br>
>> "recommendation" by putting this name into the reference<br>
>> validation-api JAR, hoping that alternative API providers (Geronimo)<br>
>> would do the same.<br>
>><br>
>> Personally I don't think there's much to loose by putting a<br>
>> recommendation into a spec appendix. If needed, the name can change<br>
>> when making it a mandatory thing in a future revision.<br>
>><br>
>> Thoughts?<br>
>><br>
>> --Gunnar<br>
>><br>
>><br>
>> 2017-05-03 22:35 GMT+02:00 Emmanuel Bernard <<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a>>:<br>
>> > -1 on the EE prefix. Bean Validation is not (only) a EE spec.<br>
>> ><br>
>> > On 3 May 2017, at 20:26, Michael Nascimento <<a href="mailto:misterm@gmail.com">misterm@gmail.com</a>> wrote:<br>
>> ><br>
>> > I know it's late to reply to this, but seems fine. I'd consult the Java<br>
>> > EE<br>
>> > EG just to make sure they don't want to use a <a href="http://javax.ee" rel="noreferrer" target="_blank">javax.ee</a> prefix (which<br>
>> > seems<br>
>> > odd, though). Using the predominant/"root" package for the module is<br>
>> > what<br>
>> > I'd recommend too.<br>
>> ><br>
>> > Regards,<br>
>> > Michael<br>
>> ><br>
>> > On Fri, Apr 21, 2017 at 10:22 AM, Gunnar Morling <<a href="mailto:gunnar@hibernate.org">gunnar@hibernate.org</a>><br>
>> > wrote:<br>
>> >><br>
>> >> Hi,<br>
>> >><br>
>> >> Java 9 is still in the works, so it's too early to put anything final<br>
>> >> into the BV spec, but should we add a recommended module name for API<br>
>> >> modules?<br>
>> >><br>
>> >> My thinking is to have a short appendix stating:<br>
>> >><br>
>> >> "Implementors that wish to provide the Bean Validation API in form<br>
>> >> of a Java 9 module,<br>
>> >> should use the module name "javax.validation". A mandatory module<br>
>> >> name will be<br>
>> >> defined in a future revision of this specification".<br>
>> >><br>
>> >> A commonly agreed on module name is required by Jigsaw to ensure<br>
>> >> different API modules (e.g. the reference one and the one provided by<br>
>> >> Apache) are interchangeable.<br>
>> >><br>
>> >> I expect further changes to the spec to support Java 9 down the road<br>
>> >> (e.g. to resolve message bundles in client modules and to provide a<br>
>> >> way for passing in a Lookup granting private access (see [1]), but<br>
>> >> it's nothing we can bake into the spec yet.<br>
>> >><br>
>> >> Thoughts?<br>
>> >><br>
>> >> --Gunnar<br>
>> >><br>
>> >> [1]<br>
>> >><br>
>> >> <a href="http://in.relation.to/2017/04/11/accessing-private-state-of-java-9-modules/" rel="noreferrer" target="_blank">http://in.relation.to/2017/04/<wbr>11/accessing-private-state-of-<wbr>java-9-modules/</a><br>
>> >> ______________________________<wbr>_________________<br>
>> >> beanvalidation-dev mailing list<br>
>> >> <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.<wbr>jboss.org</a><br>
>> >> <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/<wbr>beanvalidation-dev</a><br>
>> ><br>
>> ><br>
>> > ______________________________<wbr>_________________<br>
>> > beanvalidation-dev mailing list<br>
>> > <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.<wbr>jboss.org</a><br>
>> > <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/<wbr>beanvalidation-dev</a><br>
>> ><br>
>> ><br>
>> > ______________________________<wbr>_________________<br>
>> > beanvalidation-dev mailing list<br>
>> > <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.<wbr>jboss.org</a><br>
>> > <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/<wbr>beanvalidation-dev</a><br>
>> ______________________________<wbr>_________________<br>
>> beanvalidation-dev mailing list<br>
>> <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.<wbr>jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/<wbr>beanvalidation-dev</a><br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> beanvalidation-dev mailing list<br>
> <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.<wbr>jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/<wbr>beanvalidation-dev</a><br>
______________________________<wbr>_________________<br>
beanvalidation-dev mailing list<br>
<a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.<wbr>jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/<wbr>beanvalidation-dev</a><br>
</div></div></blockquote></div><br></div>