<div><div>if everything is fine in an application, you won't see issues with package annotations.</div><div><br></div><div>that users aren't used to it is an important part, because package annotations are quite hidden and usually unexpected.</div>
<div>esp. because they are quite unexpected, it can happen pretty easily e.g. during a refactoring/cleanup/... that the application behaves differently afterwards, but you don't recognize it immediately and later on most people just check the history of config file/s (and not the package-info).</div>
<div><br></div><div>@ "... the first version found ...":</div><div>yes - the behaviour you described is correct, but that's imo even worse. such issues are sometimes hard enough with classes (e.g. there are ee-servers which behave differently depending on the names of the archives -> something can work in application x and in application y there is the same setup but it fails due to different archive-names). since such issues are around for years a lot of people know about them, but imo issues caused by package annotations are harder to find, because package annotations are just unexpected and it's hard(er) to find the meta-data if it's e.g. a leftover in a different jar than the one you are looking at.</div>
<div><br></div><div>fyi: mark just told me that the cdi-eg dropped package annotations as well.</div><div><br></div><div>regards,</div><div>gerhard</div></div><div><br></div><div><br></div><div><br></div><div class="gmail_quote">
2012/12/13 Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>Having multiple definitions of package annotations for a given package (via split packages) is equivalent to having the same class name used twice in a split package. The first version found in your class path is the one used by the VM. </div>
<div>I don't think we should use a different rule. And to me the same class define twice is of the same level of error as a package-info.java defined twice for the same package. </div><div><div class="h5"><div><br>On 13 déc. 2012, at 16:40, Matt Benson <<a href="mailto:mbenson@apache.org" target="_blank">mbenson@apache.org</a>> wrote:<br>
<br></div><blockquote type="cite"><div>I think folk not being used to package annotations was a big part of Gerhard's objections, but what I personally find more problematic is the fact that multiple jars could conceivably include annotations for the same package. We might respond to that with a rule that a package annotation is only applied to the archive in which it is found, but then, AFAICT, an implementor would have to resort to bytecode analysis in order to sort out which setting applies to which jar. That could be more cleanly done by using a resource-based mechanism for package configs per containing jar, but then we're left with the IMO somewhat ugly situation of disparate mechanisms for package config vs. everything else.<br>
<br>Matt<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 13, 2012 at 3:28 AM, Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Wed 2012-12-12 21:02, Gerhard Petracek wrote:<br>
> i had a nice discussion with matt.<br>
> since bv 1.0 only supports one validation.xml, i'm ok with a package config<br>
> in validation.xml.<br>
> however, package annotations are in most cases just unexpected (and<br>
> error-prone).<br>
> (e.g. in deltaspike we dropped such annotations because of that.)<br>
<br>
</div>I am curious about that. What makes you say that? What made them<br>
error-prone for Deltaspike?<br>
You mean unexpected because people are not used to them?<br>
<span><font color="#888888"><br>
Emmanuel<br>
</font></span><div><div>_______________________________________________<br>
beanvalidation-dev mailing list<br>
<a href="mailto:beanvalidation-dev@lists.jboss.org" target="_blank">beanvalidation-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
</div></div></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>beanvalidation-dev mailing list</span><br><span><a href="mailto:beanvalidation-dev@lists.jboss.org" target="_blank">beanvalidation-dev@lists.jboss.org</a></span><br>
<span><a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a></span><br></div></blockquote></div></div></div><br>_______________________________________________<br>
beanvalidation-dev mailing list<br>
<a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
<br></blockquote></div><br>