Spring WAR doesn't create BuildProperties Bean

Question

I'm doing a bit of a conversion on one of my project artifacts so that we can run it with spring boot instead of only deploying to jboss, as well as adding actuators. This has gone excellently, but in the process of making everything work on spring boot, I've broken the ability to deploy the WAR to jboss.

Specifically, I've added BuildInformation to our deployment information endpoint. Based on my understanding of actuators and build-info.properties creation, as well as literally every google result I've found while trying to find someone else with this problem, what I'm doing currently should be working. I have

 compile 'org.springframework.boot:spring-boot-starter-actuator'

in my subprojects section of gradle for my platform-level project (along with every other spring-boot dependency we use). The springBoot task is configured to run buildInfo(). The resultant WAR file has the build-info.properties file under /WEB-INF/classes/META-INF/. Everything appears to be put together exactly like it's supposed to be. And yet:

13:09:59,517 ERROR [org.springframework.web.servlet.DispatcherServlet] (ServerService Thread Pool -- 53) Context initialization failed: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'pingController' defined in VFS resource ["<snip>/PingController.class"]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.springframework.boot.info.BuildProperties' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}

Any thoughts on where I should be looking?

Lakatos Gyula · Accepted Answer · 2018-11-22 11:42:05Z

2

Despite the class with the main method being annotated with @SpringBootApplication, autoconfigure still wasn't being enabled when packaged into a WAR. I added @EnableAutoConfiguration on my root @Configuration class and everything ended up working.

edited Nov 22, 2018 at 11:42

Lakatos Gyula

4,1907 gold badges38 silver badges61 bronze badges

answered Dec 13, 2017 at 21:02

ChickenWing

7039 silver badges27 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

M. Deinum Over a year ago

The class with the main doesn't do anything in a WAR unless you are also extending SpringBootServletInitializer.

ChickenWing Over a year ago

I'm fairly certain it was

Poutrathor · Accepted Answer · 2020-07-16 21:49:21Z

If anyone found this, my issue is that when the IDE is building the code, I don't have the a build properties but if I run 'maven install' from the console or from a maven tool windows in Intellij, Spring will create the BuildProperties build. I suspect the IDE might take some shortcuts. For example, the build timestamp stays at the last "true" build.

Using Intellij, Maven panel is displayed by clicking at View > Tools Windows > Maven . Then open lifecycle and right click the maven goal you wanna run (install most often) and run

Collectives™ on Stack Overflow

Spring WAR doesn't create BuildProperties Bean

2 Answers 2

2 Comments

Comments

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Related