Activity - Runtime Infrastructure - Golden Code Redmine

Activity

From 07/27/2023 to 08/25/2023

08/25/2023

01:20 PM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: Hynek Cihlar wrote:
> Greg Shah wrote:
> > Hynek/Constantin: Any objection to the merge?
>
> No objection here.
... Constantin Asofiei
12:49 PM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: Greg Shah wrote:
> Hynek/Constantin: Any objection to the merge?
No objection here.
Hynek Cihlar
09:38 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: Thanks! I was struggling badly with that possessive 's :) It's good. Galya B
09:36 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: > Check the new Logging section [[p2j:Logging#Interference-with-External-Java-Application-Logging|Interference with c... Greg Shah
09:24 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: Check the new Logging section [[p2j:Logging#Interference-with-External-Java-Application-Logging|Interference with cus... Galya B
08:59 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: Yep, yep, I forgot we have relevant documentation... Working on it. Galya B
08:59 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: Since we add our own slf4j override implementation, it can affect many customers. This would be unexpected. Adding ... Greg Shah
08:56 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: > There is no change for customers who don't experience problems with their own Java logging. If they have their own ... Greg Shah
08:50 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: There is no change for customers who don't experience problems with their own Java logging. If they have their own Ja... Galya B
08:48 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: Hynek/Constantin: Any objection to the merge?
Galya: What documentation do we need to explain this? Greg Shah
08:37 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: Right. It has to be merged. It separates slf4j implementation in its own jar, but builds in the same way. Can be remo... Galya B
08:33 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: Don't we need to do something with 7589a? Greg Shah
07:45 AM Bug #7589 (Review): org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: This should be considered resolved. Allowing the customer to include in the classpath their slf4j implementation and ... Galya B

08/21/2023

12:54 PM Bug #7649 (Closed): logging level for ScanDriver's "Failure in file" must be sever to log the sta...: Greg Shah
09:16 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: Branch 7649a was merged to trunk rev 14703. Constantin Asofiei
09:10 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: Yes Greg Shah

08/18/2023

04:26 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: Can we merge this to trunk? Constantin Asofiei

08/11/2023

10:50 AM Feature #7675: add missing runtime support for 4GL command line parameters: Some of the 4GL command line parameters which we can specify (in either the directory or as a bootstrap config value)... Greg Shah
10:02 AM Feature #7675 (New): add missing runtime support for 4GL command line parameters: Greg Shah

08/01/2023

09:28 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: Code Review Task Branch 7649a Revision 14680
No objection. Greg Shah
09:27 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: > It will take effect if no mode is already selected for the JVM. The point of the mode will be to simply reroute the... Greg Shah
03:09 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: ops Galya B
03:08 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: This is fine.
If you find some interactive tools having inconsistent output in standalone, then we should do as I ... Galya B
03:02 AM Bug #7649 (Review): logging level for ScanDriver's "Failure in file" must be sever to log the sta...: Created task branch 7649a from trunk rev 14679.
The fix is in 7649a rev 14680. Constantin Asofiei
03:00 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: Galya B wrote:
> On trunk @Failure in file@ is:
>
> [...]
>
> But maybe you've already reworked it on another ... Constantin Asofiei
02:59 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: On trunk @Failure in file@ is:... Galya B
02:57 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: In this case (ScanDriver is used by conversion) FWD uses @CentralLoggerFallback@, which has a default logging level o... Constantin Asofiei
02:56 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: An important side note: @Failure in file@ at the moment is not logged in any way way, it's simple System.out.println.... Galya B
02:54 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: With standalone tools I was cautious to convert all @System.out@ prints to logs, because when these run in standalone... Galya B
02:44 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: There are two places in @ScanDriver@ where a @Failure in file@ parsing problem may be encountered - both these need t... Constantin Asofiei
02:38 AM Bug #7649 (Closed): logging level for ScanDriver's "Failure in file" must be sever to log the sta...: Constantin Asofiei

Also available in: Atom