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 override the scope, but not sure if that is the correct answer for all deployments. Martijn On Thu, Mar 12, 2020 at 3:17 PM Martin Grigorov <mgrigo...@apache.org> wrote: > 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. > > https://github.com/apache/wicket/blob/1245ee2998930f3b9169ca8afa4018d49e2346e4/pom.xml#L221-L226 > -- Become a Wicket expert, learn from the best: http://wicketinaction.com
