hankolerd commented on PR #392: URL: https://github.com/apache/maven-antrun-plugin/pull/392#issuecomment-6065064816
> What about just enabling thread name at logger level? sounds more relevant than breaking the message no? Hi @rmannibucau , can you expand on this suggestion more please? Apologies but I am not understanding exactly what solution you are proposing as an alternative. Even when enabling Ant thread logging, Ant produces thread names like `Thread-1`, `Thread-2`, because Ant is a forked process, while Maven Multi-thread builds produce thread names like `mvn-builder-module-1`, `mvn-builder-module-2`. So an Ant process forked from module-1, it is not trivial with Multi-thread Maven builds on large reactors, to correlate which Ant Thread was is correlated to each module. This PR enhances Ant's log emitter when running in a maven multi-thread build to also emit the `mvn-builder-*` thread prefix in the emitted logs, so it is easier to trace which Maven module the forked Ant thread belongs to. If there already exists a way to achieve direct correlation between which Maven module owns the forked Ant Thread logs, I would love to hear about that. The known workarounds I am aware of; 1. Do not use Maven multi-thread builds, so that forked process logged output is linear 2. Use Maven Daemon (`mvnd`) which internally redirects each module logs and organizes the final log output as if the build had run single thread -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
