he main issue now is that my resource class creates a conflict that did not exist with the jetty:run

The log from resteasy-jaxrs is (note I added a few debug statement to track the loaded classes)

REGISTER PROVIDER BODY READER =====> com.mzt.services.SuperJAXBProvider
REGISTER PROVIDER BODY WRITER =====> com.mzt.services.SuperJAXBProvider
FOUND JAX-RS resource: com.mzt.services.HelloServiceImpl
FOUND JAX-RS resource: com.mzt.core.HelloeImpl
:WARN: failed ContextHandler@b31a7c

{/services,file:/D:/development/projects/Res tEasy/services/target/resteasy-service/}

:WARN: failed ContextHandlerCollection@8fcc7b
:WARN: failed HandlerCollection@b9b618
:INFO: Started SelectChannelConnector @ 0.0.0.0:9095
:WARN: failed Server@1d7fc31
[INFO] Jetty server exiting.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failure

Embedded error: Class is not a root resource. It, or one of its interfaces must be annotated with @Path: com.mzt.core.HelloeImpl implements: com.mzt.core.Helloe

In this case, I do not want to use the @Path notation as it is not a root class but a resource class with @GET methods in it.

The strange thing is that with the jetty:run, everything was working well beside the fact that the added @Provider were not picked up. In this case it looks like the system is confused and think that my HelloeImpl must be a root class.
Adding the @Path on the class removes the error but then the access via URL to HelloImpl does not work at all and causes a NullPointerException