gnodet commented on PR #713: URL: https://github.com/apache/maven/pull/713#issuecomment-1096753451
> > Uuuh, we have already burned ourselves with TLS. Is this really necessary? > > I'd be happy to find another solution, but the revert would introduce back a TLS anyway, without actually fixing the original problem. One possibility, but not short term, would be to deprecate `MavenSession#getCurrentProject()` and create a new interface that for the execution context which would hold the session, the current project and the current mojo execution. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
