-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
3.1.5.Final
-
None
-
-
Undefined
A Weld SE-Container that has bean discovery disabled, no bean classes, no packages to scan and only extensions, throws an IllegalStateException upon start, because beans.xml is missing:
WELD-ENV-000016: Missing beans.xml file in META-INFWELD-ENV-000016: Missing beans.xml file in META-INFjava.lang.IllegalStateException: WELD-ENV-000016: Missing beans.xml file in META-INF at org.jboss.weld.environment.se.Weld.initialize(Weld.java:773) at org.jboss.weld.junit.AbstractWeldInitiator.initWeldContainer(AbstractWeldInitiator.java:502) at org.jboss.weld.junit5.WeldInitiator.initWeld(WeldInitiator.java:193) at org.jboss.weld.junit5.WeldJunit5Extension.starWeldContainerIfAppropriate(WeldJunit5Extension.java:272) at org.jboss.weld.junit5.WeldJunit5Extension.beforeEach(WeldJunit5Extension.java:200) at [...]
This is a problem in situations where I want the only beans to come from the extension(s), for example in a JUnit-test for the extension(s).