-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lot's of DEBUG output with 2023-09 packages and p2 directory application #65
Comments
@HannesWell Do you happen to know if I can supply a system property to silence the DEBUG log output? I suspect that the M2E Logback configuration is not getting applied in this mode. |
I think I found a workaround:
and then later:
However, it would be nice if changes like aren't introduced. We have scripts for automatted/unattended installations and the additional log output breaks the parsing. I still see:
But I suspect that's something that cannot be suppressed. |
I'm not aware of one and didn't found one after a quick look at https://logback.qos.ch/manual/configuration.html, only those you already used to specify the file.
From M2E side actually nothing changed as far as I can tell. The only thing that 'changed' is that the logging is now working. It could be (partially) broken in the previous release but it should have worked before. In general it would probably help, if m2e would not supply a configuration, but would apply its changes required for the Maven Console on top of a configuration defined/supplied by the product respectively its creator in the usual ways. Then the main configuration is considered regardless of if the m2e.logback configuration is applied or not. I have suggested this already a few times, but didn't have the time yet to implement that. |
That's right. This is print-out from Apache Aries, the Service Loader Mediator Spec implementation used for the Eclipse-Platform. |
This does not appear to be an issue that can be addressed by the Eclipse Package Project itself. |
Steps to repeat:
There is now lot's of debug out like:
It looks like full HTTP transfer data is being logged.
The text was updated successfully, but these errors were encountered: