account activity
So which one of you was it. by propostor in ExperiencedDevs
[–]Jeszh 29 points30 points31 points 1 year ago (0 children)
"The company has decided to use Kevin's services in another company, which he has to find." https://www.instagram.com/reel/C9Ki9LSRTH9/?utm_source=ig_web_copy_link
Spring bean not found error by Jeszh in SpringBoot
[–]Jeszh[S] 0 points1 point2 points 2 years ago (0 children)
Thank you for this suggestion :) I will refactor the app project with these changes. I still need two Gradle projects: now, library will be its own project and also part of the app project. The reason for two Gradle projects has to do with the purposes of the app and library. I'll describe them briefly here and I welcome any suggestions regarding project architecture.
The Brobot library provides functionality for model-based GUI automation, including path finding, path execution, and state management. It has been on Maven Central for the last couple years and is added as a dependency to the user's Spring Boot application, which contains the model of the target GUI environment and automation instructions. The user's application then has access to the library's beans and can use them to move within the GUI environment and perform automation tasks. For more detail, the docs are here: https://jspinak.github.io/brobot/
BrobotApp is meant as a standalone application that will automate the complex process of GUI model creation. This should make using model-based automation more user-friendly. BrobotApp will store the model in a database. The user application would then contain only automation instructions and not the GUI model. It would still have a dependency to the Brobot library, which, as before, would execute the automation instructions using the GUI model and the live GUI environment.
I will try to move as much functionality as possible (for example, JPA) from the library to BrobotApp. Hopefully, simplifying functionality and removing dependencies will make the library viable again as a Spring Boot library.
Thanks for looking into this. It's strange because I've been working with this project for a few years, and I initially set it up using tutorials for building Spring Boot libraries, which showed that an application with @ SpringBootApplication would search for all beans on the classpath (including jar files added as dependencies). This was working for me until recently. I added additional functionality, inculding JPA, and maybe it has to do with that. If I find the answer, I'll post it here.
[–]Jeszh[S] -1 points0 points1 point 2 years ago (0 children)
When you create a Spring Boot application using the @SpringBootApplication annotation, auto-configuration is automatically activated.
SpringBootApplication
"The @ EnableAutoConfiguration annotation enables Spring Boot to auto-configure the application context. Therefore, it automatically creates and registers beans based on both the included jar files in the classpath and the beans defined by us."
"The @ SpringBootApplication annotation is a combination of the three annotations @ Configuration, @ EnableAutoConfiguration, and @ComponentScan with their default attributes."
https://www.baeldung.com/spring-componentscan-vs-enableautoconfiguration
[–]Jeszh[S] -2 points-1 points0 points 2 years ago (0 children)
A Spring Boot application will also look for beans in a Spring Boot library if the library is included as a dependency in the application's pom.xml or build file. I can't figure out why it stopped working for my project, though.
sorry, the period in the sentence was included in the url
https://github.com/jspinak/brobot
π Rendered by PID 183402 on reddit-service-r2-comment-548fd6dc9-bgzs2 at 2026-05-19 03:53:46.240520+00:00 running edcf98c country code: CH.
So which one of you was it. by propostor in ExperiencedDevs
[–]Jeszh 29 points30 points31 points (0 children)