Separate logs for separate configurations #1630
haydenbaker
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
I think the problem stems from this piece of code The logger is set as a Gradle BuildService which treats it as a singleton for the whole build. Given that the root project is initialized before the children results in the logger pointing to the root's build and reused by the children. Some releases ago we switched to using a build service because:
We'd have to re-evaluate how to handle multiple configurations on a multi-project build as the current implementation won't let you do what you want i.e, invoking the plugin in multiple projects as part of the same build session. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are using the gradle plugin in our project. We have a repository where we have a JReleaser configuration in the root (for release jars), and a separate JReleaser configuration within one of the subprojects (for releasing a CLI).
If we decide to run a full release for both "projects" concurrently, it would be nice to have the
trace.log
file be generated in each project's respectivebuild/
folder. Currently (at least with configs), only a single log file gets generated at the root build-dir, and the logs are interlaced, which makes it difficult to read through.Beta Was this translation helpful? Give feedback.
All reactions