解决Eclipse运行TestNG时Helidon启动的WELD-001335依赖歧义异常

问题场景 #

在Eclipse IDE中运行TestNG测试时，触发AmbiguousResolutionException: WELD-001335异常，导致Helidon服务器无法启动，但执行mvn clean package时完全正常。具体异常栈如下：

Caused by: org.jboss.weld.exceptions.AmbiguousResolutionException: WELD-001335: 类型PersistenceProvider存在依赖歧义，限定符为
  可能的依赖项:
  - Configurator Bean [class io.helidon.integrations.cdi.jpa.JpaExtension, types: PersistenceProvider, Object, DelegatePersistenceProvider, LogPersistenceProvider, qualifiers: @Any @Default],
  - Configurator Bean [class io.helidon.integrations.cdi.jpa.JpaExtension, types: PersistenceProvider, qualifiers: @Default @Any @Named]
    at org.jboss.weld.bean.builtin.InstanceImpl.checkBeanResolved(InstanceImpl.java:244)
    at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:113)
    at org.jboss.weld.util.ForwardingWeldInstance.get(ForwardingWeldInstance.java:44)
    at io.helidon.integrations.cdi.jpa.EntityManagerFactories.getPersistenceProvider(EntityManagerFactories.java:222)
    at io.helidon.integrations.cdi.jpa.EntityManagerFactories.createContainerManagedEntityManagerFactory(EntityManagerFactories.java:161)
    at io.helidon.integrations.cdi.jpa.JpaExtension.lambda$addContainerManagedEntityManagerFactoryBeans$1(JpaExtension.java:1033)
    at org.jboss.weld.bootstrap.events.configurator.BeanConfiguratorImpl$CreateCallback.create(BeanConfiguratorImpl.java:372)
    at org.jboss.weld.bootstrap.events.configurator.BeanConfiguratorImpl$CreateCallback.access$700(BeanConfiguratorImpl.java:339)
    at org.jboss.weld.bootstrap.events.configurator.BeanConfiguratorImpl$ImmutableBean.create(BeanConfiguratorImpl.java:511)
    at org.jboss.weld.contexts.AbstractContext.get(AbstractContext.java:96)
    at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
    at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
    at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:102)
    at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:105)
    at io.helidon.integrations.cdi.jpa.EntityManagerFactory$_$$_WeldClientProxy.isOpen(Unknown Source)
    at io.helidon.integrations.cdi.jpa.JpaExtension.onStartup(JpaExtension.java:2053)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:569)
    at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
    at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
    at org.jboss.weld.injection.MethodInvocationStrategy$DefaultMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:144)
    at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
    at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123)
    at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
    at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
    at jakarta.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:125)
    at org.jboss.weld.util.Observers.notify(Observers.java:166)
    at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285)
    at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:273)
    at org.jboss.weld.event.EventImpl.fire(EventImpl.java:96)
    at io.helidon.microprofile.cdi.HelidonContainerImpl.doStart(HelidonContainerImpl.java:340)
    at io.helidon.common.context.Contexts.runInContext(Contexts.java:137)
    at io.helidon.microprofile.cdi.HelidonContainerImpl.start(HelidonContainerImpl.java:250)
    at io.helidon.microprofile.server.ServerImpl.start(ServerImpl.java:76)

问题原因 #

异常核心是CDI容器（Weld）发现有两个PersistenceProvider类型的Bean都匹配@Default和@Any限定符：一个带有@Named注解，一个没有。Maven打包时的类路径扫描、CDI初始化逻辑和Eclipse TestNG运行环境存在差异，导致后者触发了依赖歧义。

解决方案 #

1. 明确指定注入的Bean #

在需要注入PersistenceProvider的代码处，通过限定符明确指定要使用的Bean。如果需要带@Named的实例，直接添加注解：

@Inject
@Named
private PersistenceProvider persistenceProvider;

如果不需要带@Named的实例，可以自定义限定符标记目标Bean，或者使用@Priority设置优先级让容器优先选择某一个。

2. 修正Eclipse的TestNG运行配置 #

• 打开TestNG运行配置，检查类路径标签页，移除重复的依赖JAR或项目模块，确保只包含必要的依赖。
• 右键项目 → Maven → Update Project，勾选Force Update of Snapshots/Releases，让Eclipse严格遵循Maven的依赖配置，避免本地类路径混乱。

3. 调整CDI配置排除歧义 #

在项目的beans.xml中，通过<alternatives>标签指定优先使用的Bean，或者排除不需要的实例：

<beans xmlns="http://xmlns.jcp.org/xml/ns/javaee"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd"
       version="2.0">
    <!-- 指定优先使用不带@Named的JpaExtension Bean -->
    <alternatives>
        <class>io.helidon.integrations.cdi.jpa.JpaExtension</class>
    </alternatives>
</beans>

4. 清理Eclipse缓存 #

• 执行Project → Clean...，选择目标项目清理编译文件。
• 备份后删除工作区.metadata目录下的缓存文件，重新导入项目，彻底清除Eclipse的缓存冲突。

内容的提问来源于stack exchange，提问作者Nathan