enso/tools/legal-review/Table/report-state

AE474B24FC7C88ACA56C70EC19DCD5F224178089AA2910DB117EE7D914D6C7FF
239E94FB3027DA2C129E48F1B791C0FDF11D8E3E381C37DE987392FF56012106
0
Always log to console and file (#7825) * Always log verbose to a file The change adds an option by default to always log to a file with verbose log level. The implementation is a bit tricky because in the most common use-case we have to always log in verbose mode to a socket and only later apply the desired log levels. Previously socket appender would respect the desired log level already before forwarding the log. If by default we log to a file, verbose mode is simply ignored and does not override user settings. To test run `project-manager` with `ENSO_LOGSERVER_APPENDER=console` env variable. That will output to the console with the default `INFO` level and `TRACE` log level for the file. * add docs * changelog * Address some PR requests 1. Log INFO level to CONSOLE by default 2. Change runner's default log level from ERROR to WARN Took a while to figure out why the correct log level wasn't being passed to the language server, therefore ignoring the (desired) verbose logs from the log file. * linter * 3rd party uses log4j for logging Getting rid of the warning by adding a log4j over slf4j bridge: ``` ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console... ``` * legal review update * Make sure tests use test resources Having `application.conf` in `src/main/resources` and `test/resources` does not guarantee that in Tests we will pick up the latter. Instead, by default it seems to do some kind of merge of different configurations, which is far from desired. * Ensure native launcher test log to console only Logging to console and (temporary) files is problematic for Windows. The CI also revealed a problem with the native configuration because it was not possible to modify the launcher via env variables as everything was initialized during build time. * Adapt to method changes * Potentially deal with Windows failures 2023-09-26 12:32:04 +03:00			`AE474B24FC7C88ACA56C70EC19DCD5F224178089AA2910DB117EE7D914D6C7FF`
Add AWS SSO JARs to the `Standard.AWS` library (#9782) As reported by our users, when using the AWS SSO, our code was failing with: ``` Execution finished with an error: To use Sso related properties in the 'xyz' profile, the 'sso' service module must be on the class path. ``` This PR adds the missing JARs to fix that. Additionally it improves the license review tool UX a bit (parts of #9122): - sorting the report by amount of problems, so that dependencies with unresolved problems appear at the top, - semi-automatic helper button to rename package configurations after a version bump, - button to remove stale entries from config (files or copyrights that disappeared after update), - button to add custom copyright notice text straight from the report UI, - button to set a file as the license for the project (creating the `custom-license` file automatically) - ability to filter processed projects - e.g. `openLegalReviewReport AWS` will only run on the AWS subproject - saving time processing unchanged dependencies, - updated the license search heuristic, fixing a problem with duplicates: - if we had dependencies `netty-http` and `netty-http2`, because of a prefix-check logic, the notices for `netty-http` would also appear again for `netty-http2`, which is not valid. I have improved the heuristic to avoid these false positives and removed them from the current report. - WIP: button to mark a license type as reviewed (not finished in this PR). 2024-04-25 21:44:51 +03:00			`239E94FB3027DA2C129E48F1B791C0FDF11D8E3E381C37DE987392FF56012106`
Import syntax including namespace (#1806) 2021-06-24 13:42:24 +03:00			`0`