Upgrade CDI API to 2.0.Beta1

weld · Dec 15, 2016 · bf743a2 · bf743a2
1 parent a6d0270
commit bf743a2
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 1 deletion.
diff --git a/pom.xml b/pom.xml
@@ -91,7 +91,7 @@
         <!-- build.config.version>10-SNAPSHOT</build.config.version -->
 
         <atinject.api.version>1</atinject.api.version>
-        <cdi.api.version>2.0.Alpha6</cdi.api.version>
+        <cdi.api.version>2.0.Beta1</cdi.api.version>
         <ejb.api.version>1.0.0.Final</ejb.api.version>
         <jpa.api.version>1.0.0.Final</jpa.api.version>
         <validation.api.version>1.1.0.Final</validation.api.version>

diff --git a/weld-spi/src/main/java/org/jboss/weld/manager/api/WeldManager.java b/weld-spi/src/main/java/org/jboss/weld/manager/api/WeldManager.java
@@ -113,6 +113,14 @@ public interface WeldManager extends BeanManager, Serializable {
      */
     String getId();
 
+    /**
+     * TODO There is an open clarification issue CDI-671 which might affect the API design. I.e. this method might be changed in a way that breaks backward
+     * compatibility in a final version of API.
+     *
+     * @seeIssue CDI-671
+     * @return a new {@link Instance} with required type {@link Object} and no required qualifiers ({@link javax.enterprise.inject.Default} is added automatically during resolution if
+     *         no qualifiers are selected)
+     */
     Instance<Object> instance();
 
     @Override