currlent it's broken:

Yes, I know its an Alpha version, may or may not work. Just want to raise if incase unnoticed

I am unable to use following dependency.

<dependency>
    <groupId>org.jboss.resteasy</groupId>
    <artifactId>resteasy-spring-boot-starter</artifactId>
    <version>6.0.0.Alpha1</version>
</dependency>

Because I see pom.xml has relative path for parent pom.xml 'resteasy-spring-boot-starter-parent' which is not included in the above package.

Error:

Failed to read artifact descriptor for org.jboss.resteasy:resteasy-spring-boot-starter:jar:6.0.0.Alpha1: Could not find artifact org.jboss.resteasy:resteasy-spring-boot-starter-parent:pom:6.0.0.Alpha1 in *** (https://pkgs.dev.azure.com/*********/maven/v1) -> [Help 1]

• https://issues.redhat.com/browse/RESTEASY-2168

Because this becomes a requirement for spring-boot build: https://github.com/spring-projects/spring-framework/blob/v6.0.2/spring-core/src/main/java/org/springframework/core/LocalVariableTableParameterNameDiscoverer.java#L54

Because it messed up with other tests in context.

For the 4.9.x branch of the Spring Boot starter, we are having some Jackson issues when pulling this dependency along Spring Boot 2.7.x. A version of this starter compatible with Spring Boot 2.7.x will be useful. I created a PR in GitHub with some progress (#181)

Migrated from: https://issues.redhat.com/browse/RESTEASY-3206

The resteasy-spring-boot-starter pom.xml declares a dependency to Guava:

Right now Guava will be packaged as a transitive dependency for any project using the starter.

I wonder if Guava is required for the starter or can be removed.
As a test I removed the Guava dependency from the starter's pom.xml and haven't noticed any issues when running mvn verify.

Can you clarify why Guava is declared here?
Thanks!

Currently the maven install plugin is skipped, which is not correct.

https://github.com/spring-projects/spring-framework/releases/tag/v6.0.3

Before a final release we definitely need to upgrade to using the 3.1.0 version of the spec not the 3.1.0.RC1-jbossorg-1 fork.

Run:

$ mvn integration-test

Result:

move issue here.

https://github.com/resteasy/resteasy/releases/tag/6.2.2.Final

https://issues.redhat.com/browse/RESTEASY-3056

I am using this starter to expose JAX-RS resources.
Now I want to integrate Spring boot Actuator
Simply, I insert the dependency in my build.gradle

Dependency
implementation 'org.springframework.boot:spring-boot-starter-actuator'.

LOGS
INFO 1386771 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 1 endpoint(s) beneath base path '/actuator'.
But I can't access it.

Is there any alternative to access these endpoints without having to migrate to Jersey?

digging further i think i found the issue:

public class ResteasyApplicationBuilder {

	public static final String BEAN_NAME = "JaxrsApplicationServletBuilder";

	private static final Logger logger = LoggerFactory.getLogger(ResteasyApplicationBuilder.class);

	public ServletRegistrationBean build(String applicationClassName, String path, Set<Class<?>> resources, Set<Class<?>> providers) {
		Servlet servlet = new HttpServlet30Dispatcher();

		ServletRegistrationBean servletRegistrationBean = new ServletRegistrationBean(servlet);

		servletRegistrationBean.setName(applicationClassName);
		servletRegistrationBean.setLoadOnStartup(1);
		servletRegistrationBean.setAsyncSupported(true);
		servletRegistrationBean.addInitParameter(Application.class.getTypeName(), applicationClassName);

notice this line specifically:
servletRegistrationBean.addInitParameter(Application.class.getTypeName(), applicationClassName);

now look at the ServletContainerDispatcher code from resteasy core

public void init(ServletContext servletContext, ConfigurationBootstrap bootstrap, HttpRequestFactory requestFactory, HttpResponseFactory responseFactory) throws ServletException {
      this.requestFactory = requestFactory;
      this.responseFactory = responseFactory;
      ResteasyDeployment ctxDeployment = (ResteasyDeployment)servletContext.getAttribute(ResteasyDeployment.class.getName());
      ResteasyProviderFactory globalFactory = (ResteasyProviderFactory)servletContext.getAttribute(ResteasyProviderFactory.class.getName());
      if (globalFactory == null && ctxDeployment != null) {
          globalFactory = ctxDeployment.getProviderFactory();
      }

      Dispatcher globalDispatcher = (Dispatcher)servletContext.getAttribute(Dispatcher.class.getName());
      if (globalDispatcher == null && ctxDeployment != null) {
          globalDispatcher = ctxDeployment.getDispatcher();
      }

      String application = bootstrap.getInitParameter("jakarta.ws.rs.Application");

specifically

String application = bootstrap.getInitParameter("jakarta.ws.rs.Application");
while Application.class resolves to jakarta.ws.rs.core.Application causing application to allways be null

this matters because later in the ServletContainerDispatcher code we check if application is not null ,in this case we call process application which in turn calls getClasses and getSingletons

not sure if the fix should be in this repo or in the resteasy core repo