GitHub user ppkarwasz edited a discussion: Roadmap for `2.25.1` release
Hi everyone, @vy and I had a call to discuss the aftermath of the `2.25.0` release. While generally successful, we identified a few issues that affect usage in specific environments. To address these promptly, we're planning a `2.25.1` patch release in early July. This schedule also gives users time to test and report any additional feedback on `2.25.0`. ### Upcoming Releases Overview To give you a complete picture of what's ahead: * **`2.25.1`**: Early July — Patch release addressing specific regressions and edge-case issues. * **`3.0.0-beta4`**: Early August — The main blocker is #3161, which tracks the synchronization of improvements from the 2.x branch into `main`. Contributions are very welcome! * **`2.26.0`**: Early September — This release will include all improvements and bug fixes merged by then. ## 🔧 Roadmap for `2.25.1` We're targeting a small set of focused fixes that impact integration with alternative build tools and platforms: * **JBang Compatibility** (#3758, #3779): The `jspecify.version` property isn't resolvable in published parent POMs due to POM flattening. While this doesn't affect Maven or Gradle users (thanks to `provided` scope and inline metadata), it breaks tools like JBang. We'll address this in the patch. * **Gradle + Java 8** (#3754): The upgrade of `spotbugs-annotations` to a Java 11 version causes Gradle to reject `log4j-api` in Java 8 projects. Although the dependency is `compileOnly`, Gradle treats this conservatively. * **OSGi Compatibility** (#3706): Disruptor version detection currently misbehaves in OSGi environments due to improper use of TCCL. While a broader TCCL cleanup is planned for `2.26.0` (see #2850), a targeted fix will be made for this specific issue in `2.25.1`. * **Third-party Plugin Compilation** (#3755): Users building third-party Log4j plugins have reported friction due to mandatory compiler arguments (`-Alog4j.graalvm.groupId` and `-Alog4j.graalvm.artifactId`). We'll improve documentation and investigate making these arguments **optional**, possibly adopting a strategy similar to [picocli](https://github.com/remkop/picocli). Thanks for your continued feedback and contributions! > [!NOTE] > I'm sharing this roadmap both on GitHub Discussions and the `dev@logging` > mailing list. However, since synchronization is one-way, please leave any > comments **on GitHub Discussions** if possible. GitHub link: https://github.com/apache/logging-log4j2/discussions/3766 ---- This is an automatically sent email for dev@logging.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
