On Fri, Mar 13, 2020 at 10:22 AM Emond Papegaaij
wrote:
> Looking at the examples, I think the packaging currently is wrong. The
> examples package weld (cdi implementation), but rely on a provided
> cdi-api. The cdi-api should simply be added as a compile dependency to
> the examples.
>
I've
Looking at the examples, I think the packaging currently is wrong. The
examples package weld (cdi implementation), but rely on a provided
cdi-api. The cdi-api should simply be added as a compile dependency to
the examples.
Emond
On Fri, Mar 13, 2020 at 2:59 AM Maxim Solodovnik wrote:
>
> Maybe
Maybe this dependency can be added to dependencies of jetty-maven-plugin ?
On Thu, 12 Mar 2020 at 23:23, Martin Grigorov wrote:
>
> On Thu, Mar 12, 2020, 16:41 Martijn Dashorst
> wrote:
>
> > Because it is, just like the servlet-api, a specification that is provided
> > by the container. When
On Thu, Mar 12, 2020, 16:41 Martijn Dashorst
wrote:
> Because it is, just like the servlet-api, a specification that is provided
> by the container. When your container does not supply that specification,
> you have to override the scope yourself and supply the API that way. E.G.
> Wildfly
Because it is, just like the servlet-api, a specification that is provided
by the container. When your container does not supply that specification,
you have to override the scope yourself and supply the API that way. E.G.
Wildfly supplies that API, as does Glassfish, etc.
The examples could
Hi,
Does anyone know why jakarta.enterprise:jakarta.enterprise.cdi-api
dependency [1] has provided
scope in dependency management ?
I'm hitting NoClassDefFoundError
for javax.enterprise.inject.spi.BeanManager while deploying
wicket-examples.war in Tomcat.
1.
