Below is the short version first (why you no longer see the “Base dir” line) followed by a more complete Spring-Boot-2 → 3 / Spring-Cloud-Config upgrade checklist.
---
## Why the “Base dir” banner disappeared
In the Spring Cloud Config 2021.x line (the one that works with Spring-Boot 2) the class
`org.springframework.cloud.config.server.environment.JGitEnvironmentRepository`
logged
```
INFO ... Base directory: /tmp/config-repo-123456
```
In 2022.0.0 and later (first line that works with Spring-Boot 3) the maintainers
• re-worked several log messages and
• lowered this particular one from `INFO` to `DEBUG`.
So unless you changed the root log level you will not see it anymore.
You can get it back with e.g.
```yaml
# application.yml
logging:
level:
org.springframework.cloud.config.server.environment: DEBUG
# or even TRACE if you want Git command traces
```
Functionally nothing else changed with the `spring.cloud.config.server.git.basedir`
property – the repo is still cloned/updated in exactly the same location.
---
## Full upgrade checklist (Boot 2 ➜ Boot 3 + Cloud 2023.x)
1. **Dependency alignment**
* Use a Spring Boot 3.x release (preferably the latest patch, e.g. 3.2.x).
* Import the matching Spring Cloud BOM.
```xml
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-dependencies</artifactId>
<version>2023.0.3</version><!-- or newer -->
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
```
* Remove any old `spring-cloud-starter-parent` version overrides.
2. **Java version**
* Boot 3 requires **Java 17+**.
3. **Jakarta namespace**
* All `javax.*` imports become `jakarta.*`.
In a pure Config Server you rarely touch these directly, but if you have
custom filters / servlets / JPA entities you must change the imports and
upgrade any 3rd-party libs that still use `javax`.
4. **Actuator changes**
* Default management path is still `/actuator`, but several IDs changed names
(`env` → `environment`, etc.).
Verify any monitoring / Prometheus scrapers.
5. **Bootstrap deprecation**
* Since Spring Cloud 2022 the “bootstrap phase” is optional.
• You can keep `spring-cloud-starter-bootstrap`
• or move the Config import to `application.yml`:
```yaml
spring:
config:
import: "optional:configserver:"
```
6. **Configuration properties**
* `spring.cloud.config.server.git.basedir`, `uri`, `username`, `password` are unchanged.
* New properties were added (e.g. `clone-on-start`, `force-pull`). Check the
reference guide if you relied on legacy behavior.
7. **Security**
* Spring Security 6 (Boot 3) adopts `jakarta.servlet`.
If you protected your Config Server with WebSecurityConfigurerAdapter, migrate to `SecurityFilterChain` beans.
8. **Logging**
* As mentioned, many `INFO` messages have been “demoted” to `DEBUG`.
* Default logback pattern no longer includes the coloured Spring banner unless you set `spring.main.banner-mode=console`.
9. **Testing**
* Update to JUnit Jupiter 5.10+, Mockito 5+, Testcontainers 1.19+.
Older versions may still depend on `javax.*`.
10. **Container image**
* If you build OCI images with `spring-boot-maven-plugin`:
`./mvnw spring-boot:build-image` now produces a `jdk:17` stack by default
(Paketo builder `paketobuildpacks/builder-jammy-base:latest`).
---
### TL;DR
• The “Base directory” line did not disappear because the property changed –
only its log level did.
• Raise the log level to `DEBUG` if you want it back.
• When upgrading, line up Boot 3.x with Spring Cloud 2023.x, use Java 17+, fix
any `javax` imports, review actuator & security changes, and you’re good to go.