[
https://issues.apache.org/jira/browse/DELTASPIKE-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101264#comment-14101264
]
Alexandr Smirnov commented on DELTASPIKE-691:
---------------------------------------------
Exactly, I mean that. You compile (using OWB profile) against the api (geronimo
cdi api 1.0) which is not binary compatible with the another api (jboss cdi api
1.2).
That is why you have another profile in parent-code pom to run test in Weld.
Unfortunately (for me) only the code compiled with default profile is deployed
to maven central. So I have to build deltaspike myself with activated Weld
profile and deploy it to our local repository.
No problem, I can do it.
But I would like to create issue on this point, so we have artifacts in maven
central built with Weld profile activated.
> Weld 2.x support
> ----------------
>
> Key: DELTASPIKE-691
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-691
> Project: DeltaSpike
> Issue Type: Wish
> Components: Data-Module
> Affects Versions: 1.0.1
> Environment: arquillian-weld-se-embedded-1.1 unit test
> Reporter: Alexandr Smirnov
>
> java.lang.IncompatibleClassChangeError: Class
> org.apache.deltaspike.core.util.bean.ImmutablePassivationCapableBean does not
> implement the requested interface javax.enterprise.inject.spi.BeanAttributes
> at
> org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateStereotypes(ExternalBeanAttributesFactory.java:75)
> When trying to start with Weld 2.2.1
--
This message was sent by Atlassian JIRA
(v6.2#6252)
