Basically the spec text change to support this is "repeating annotations work as
qualifiers. they continue to act as inclusive, meaning those repeated annotations follow
the same resolution strategy as any other qualifiers."
Do you agree?
________________________________
From: cdi-dev-bounces(a)lists.jboss.org <cdi-dev-bounces(a)lists.jboss.org> on behalf of
Antonin Stefanutti <antonin(a)stefanutti.fr>
Sent: Thursday, November 10, 2016 1:03 PM
To: cdi-dev(a)lists.jboss.org
Subject: [cdi-dev] Repeating annotations support (CDI-460 and CDI-471)
Hi,
While CDI-471 (Support repeating qualifiers in typesafe resolution mechanism) targets CDI
2.0, related issue CDI-460 (Support repeating annotations in CDI SPI) doesn't have any
fix version defined. Can it be implied that CDI-460 will be addressed with CDI-471 or is
it intentional left undefined? IMHO, it'd be important to have CDI-460 delivered as
part of CDI 2.0 as well to bring a consistent support for repeating annotations in CDI.
Thanks,
Antonin
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
cdi-dev Info Page - JBoss
Developer<https://lists.jboss.org/mailman/listinfo/cdi-dev>
lists.jboss.org
List to discuss the development of CDI (the specification) To see the collection of prior
postings to the list, visit the cdi-dev Archives.
Note that for all code provided on this list, the provider licenses the code under the
Apache License, Version 2 (
http://www.apache.org/licenses/LICENSE-2.0.html). For all other
ideas provided on this list, the provider waives all patent and other intellectual
property rights inherent in such information.
Apache License, Version
2.0<http://www.apache.org/licenses/LICENSE-2.0.html>
www.apache.org
Apache License Version 2.0, January 2004
http://www.apache.org/licenses/ TERMS AND
CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION. 1. Definitions.
________________________________
NOTICE: This e-mail message and any attachments may contain confidential, proprietary,
and/or privileged information which should be treated accordingly. If you are not the
intended recipient, please notify the sender immediately by return e-mail, delete this
message, and destroy all physical and electronic copies. Thank you.