<div dir="ltr">BTW, my point on binary compatibility is moot. As long as we don't require app developers to implement interfaces, we can add methods all over. The impls can fix that themselves.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 19, 2014 at 10:10 AM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com" target="_blank">pmuir@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
On 19 Sep 2014, at 02:31, John D. Ament <<a href="mailto:john.d.ament@gmail.com">john.d.ament@gmail.com</a>> wrote:<br>
<br>
> Hi all<br>
><br>
> Was reading through the log from this past meeting. To comment on a couple of points:<br>
><br>
> - In JMS 2.0 we really wanted to remove the old Queue and Topic based interfaces. We received a lot of push back from even deprecating them, and the most that could be done was to add a comment to the javadoc dissuading people from using them and only keeping them around for legacy purposes. Similar to how @New is stuck around, probably forever, any existing classes need to stick around forever. When it comes to pruning, the pruning is around a technology and not just a small set of classes within a JSR.<br>
<br>
</span>Agreed, this is correct, and Antoine and I are aware of this and will make sure this is what happens.<br>
<span class=""><br>
><br>
> - In JDK8, they fixed the binary compatibility issue w/ default methods. Since CDI 2.0 should be targeting a Java 8 runtime, can we leverage that for binary compatibility, by saying any new methods we add to interfaces will be default methods some ambiguous/not very useful implementation?<br>
<br>
</span>Yes, if we decide to target Java 8.<br>
<br>
><br>
> John<br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
<br>
</blockquote></div><br></div>