FWD » Core Development » Runtime Infrastructure

04/07/2023

06:23 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> Greg, I recall we wanted to keep the com.goldencode. packages as non-dependent on com.goldencode.p2j as possible. I... Greg Shah

12:58 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Constantin Asofiei wrote:
> [...]
> can call back to the server, determine the Session ID and the FWD User, and cac... Eugenie Lyzenko

11:49 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

This is a high-level review of 5703a/14578 - I have not gone through all the files. I'll go over all files in the ne... Constantin Asofiei

10:49 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

How does disabling @LOG-MANAGER@ come into this discussion of the server log? If it can be disabled in 5 ways, that ... Greg Shah

10:31 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg, on my interview you said you're reproducing OE with the typos and all its flaws. Galya B

10:30 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> I don't see why @LOG-MANAGER@ output would ever end up in the server log.
All System.err does ... Galya B

10:26 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> As far as "disabling" @LOG-MANAGER@, I guess you mean calling @CLOSE-LOG()@?
There are 5 differ... Galya B

10:22 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> So you're suggesting that we know what log is written to clientlog and not write it to server.log?
I don't know ... Greg Shah

10:11 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> Add the empty thread id
Why is it empty?
> Is this what needs to be done?
If this is the list of deviation... Greg Shah

10:09 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> > @clientlog@ lives its own 4GL life, let's not enhance it.
>
> You are suggesting that we imp... Galya B

10:06 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> > There is this dir config (logging:file:dir) you might have noticed that allows you to choose th... Galya B

10:04 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> ** Legacy spec for @LOG-MANAGER@ output which should be completely compatible with the 4GL spec. ... Galya B

10:03 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> @clientlog@ lives its own 4GL life, let's not enhance it.
You are suggesting that we implement a 2nd logfile for... Greg Shah

10:01 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> There is this dir config (logging:file:dir) you might have noticed that allows you to choose the location. The old ... Greg Shah

09:44 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> If @clientLog@ is specified, then won't we output everything to that log?
>
> This points out ... Galya B

09:38 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> * Use the @Formatter@ conversions as much as possible and add consistent formatting options for s... Galya B

09:30 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> For example, people have very different ideas about how date and time values should be formatted.... Galya B

09:20 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> In the old internal logging approach in FWD, we could configure logging at any class or package l... Galya B

09:00 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> At the moment there are two base log levels to be configured - one for the spawner messages and one for everything ... Greg Shah

08:20 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Constantin Asofiei wrote:
> Does 5703a depend on any work from 5753d?
No Galya B

08:20 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Does 5703a depend on any work from 5753d?
Constantin Asofiei

04/06/2023

10:04 AM Bug #5703 (Review): rationalize, standardize and simplify the client-side log file name configura...

Branch 5703a, r14578 based on trunk r14523. Review with @bzr diff -r-56@. More on how to test in #5703#note-161. Galya B

07:45 AM Bug #5701 (Closed): logfile names for -O outputToFile use the spawner pid instead of the Java (FW...

Greg Shah

04/05/2023

03:03 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

The following System.err usages are related to #7180:
* cmd line args -err, -warn in com.goldencode.p2j.preproc.Prep... Galya B

04/04/2023

10:01 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Branch 5703a, r14573 is ready for a pre-final code review. There are still no file headers and I need to go through a... Galya B

09:38 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

It should be though that it's not in use any more. I'll remove it. Galya B

09:37 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

I will run the dependency tree generation and confirm my statement that no class is explicitly imported, but I'm aski... Galya B

09:36 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Roger Borrello wrote:
> How about @./gradlew dependencies@?
Thanks, I see only root references for @+--- org.jboss.... Constantin Asofiei

09:33 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Constantin Asofiei wrote:
> Roger, I can't find the build dependency tree for all the jar libraries - is this somewh... Roger Borrello

07:16 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

@fwdspi.jar@ doesn't include the logging classes and @FwdCollatorProvider@ fails runtime. I'm not sure how/when the c... Galya B

06:50 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Galya Bogdanova wrote:
> Does someone know why is this dependency in build.gradle: @fwdConvertServer group: 'org.jbo... Constantin Asofiei

06:46 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Does someone know why is this dependency in build.gradle: @fwdConvertServer group: 'org.jboss.logging', name: 'jboss-... Galya B

06:44 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Constantin Asofiei wrote:
> There is a script named @gen_headers.py@ in @~/usrbin@, as part of the standard dev setu... Galya B

04/03/2023

10:22 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Galya Bogdanova wrote:
> There are changes in 486 files and more to come. Am I expected to update all file headers?
... Constantin Asofiei

10:18 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

There are changes in 486 files and more to come. Am I expected to update all file headers? Galya B

03/30/2023

07:23 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Galya Bogdanova wrote:
> Merged to trunk as r14521. It also fixes the repeating of log messages mentioned in #5753#n... Constantin Asofiei

07:13 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Merged to trunk as r14521. It also fixes the repeating of log messages mentioned in #5753#note-79.
Do I have to wr... Galya B

06:57 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Galya Bogdanova wrote:
> I was able to reproduce the issue with the hanging appserver and it's fixed in 5701d as I'v... Constantin Asofiei

04:45 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

I was able to reproduce the issue with the hanging appserver and it's fixed in 5701d as I've mentioned earlier. Do I ... Galya B

04:14 AM Bug #5701 (Review): logfile names for -O outputToFile use the spawner pid instead of the Java (FW...

Galya B

02:56 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Galya Bogdanova wrote:
> Constantin Asofiei wrote:
> > Keep in mind this is with the 5701d fix and FWD trunk. So F... Constantin Asofiei

02:43 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

I added some missing messages to the clientlog for #5753. Galya B

02:37 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

I think I did something to the repeated constructor msg, but atm not 100% sure. Galya B

02:35 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Constantin Asofiei wrote:
> Keep in mind this is with the 5701d fix and FWD trunk. So FWD trunk loses some MESSAGE ... Galya B

02:18 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Galya, the changes in 5701d look OK.
Regarding your issue: I've checked your test and the @hello@ you see in the a... Constantin Asofiei

04:12 AM Bug #7236: Inconsistencies in stderr and logs related to MESSAGE and AppError constructor

To be addressed after the merge of #5701, #5753 and #5703.
Steps to reproduce in #5701#note-86.
Issues:
* The ... Galya B

04:04 AM Bug #7236 (New): Inconsistencies in stderr and logs related to MESSAGE and AppError constructor

Galya B

03/29/2023

09:12 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Constantin, I think it is good to go... for 3rd time. 3rd time should be the lucky one. Galya B

09:10 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Ok, that's straight weird. Every third run of the same procedure (without deleting the output to files) writes the fi... Galya B

09:00 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

I've found a weird behavior just now. If the @output to@ file is already existing, the text goes to @outputToFile@ in... Galya B

08:56 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Constantin Asofiei wrote:
> Did you test the batch client with a program using @OUTPUT TO somefile.txt@?
Yes. I'v... Galya B

08:36 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Galya, try this for appserver connect @-AppService app_server -S 21200 -H localhost -sessionModel Session-free -Direc... Constantin Asofiei

06:06 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Otherwise chui (terminal / swing) and batch work fine - generate the file and output any other display text. Galya B

05:46 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Constantin Asofiei wrote:
> Galya: please do some tests in batch/appserver/ChUI, with code like this:
> [...]
If... Galya B

02:19 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Galya Bogdanova wrote:
> Lol. My... Is this the overwrite message warning for... I haven't set this myself.
If some... Constantin Asofiei

03/28/2023

11:48 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

... Galya B

11:45 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

I didn't receive notification for the notes from my last comment, so let me get up to date... Galya B

11:42 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Constantin Asofiei wrote:
> Please prepare these changes in 5701c, and check if the @filesys.c@ native code can be a... Galya B

11:08 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Greg, I think you are right. This may affect the redirected terminal in both ChUI and batch processes.
For batch ... Constantin Asofiei

11:07 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Greg Shah wrote:
> The 4GL knows when its STDIO is redirected and it changes its behavior based on that. I think we... Eugenie Lyzenko

10:57 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

The 4GL knows when its STDIO is redirected and it changes its behavior based on that. I think we implemented the @Ja... Greg Shah

10:47 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Constantin Asofiei wrote:
> Please prepare these changes in 5701c, and check if the @filesys.c@ native code can be a... Galya B

10:42 AM Bug #5701 (WIP): logfile names for -O outputToFile use the spawner pid instead of the Java (FWD c...

Galya Bogdanova wrote:
> Even better if @IS_OUTPUT_REDIRECTED@ is moved to @FileChecker@.
Please prepare these chan... Constantin Asofiei

10:41 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Even better if @IS_OUTPUT_REDIRECTED@ is moved to @FileChecker@. Galya B

10:39 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Constantin Asofiei wrote:
> This patch seems to solve the issue:
> [...]
>
> But I don't know if this is the cor... Galya B

10:37 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Constantin, this is troublesome. With #5701 stdout is not redirected in the native code, but programmatically in Java... Galya B

10:37 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

This patch seems to solve the issue:... Constantin Asofiei

10:33 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Galya Bogdanova wrote:
> Constantin Asofiei wrote:
> > This can be seen with appservers, where there is a @MESSAGE ... Constantin Asofiei

10:29 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Constantin Asofiei wrote:
> This can be seen with appservers, where there is a @MESSAGE "Message" VIEW-AS ALERT-BOX... Galya B

10:26 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Galya, there is a regression in trunk revs 14506/14507.
This can be seen with appservers, where there is a @MESS... Constantin Asofiei

04:53 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

The Session/Thread/User combo context came as ported from LogHelper where it was used only for some logs. I tried to ... Galya B

04:33 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

A few remarks about the identification of to who a log message belongs:
* @SERVER, Session:00000007, Thread:0000001F... Constantin Asofiei

03/23/2023

12:53 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Constantin Asofiei wrote:
> Correct, FWD doesn't have a broker in OE terms. The broker is used only for remote laun... Greg Shah

10:56 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

I'm posting sample log files for format review.
First a few explanations:
- I've set up the infrastructure for lo... Galya B

06:40 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Correct, FWD doesn't have a broker in OE terms. The broker is used only for remote launching; Greg, I think any log ... Constantin Asofiei

03:19 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Constantin Asofiei wrote:
> Please describe what broker log content you refer to. You mean the case when the appser... Galya B

03/22/2023

02:55 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Galya Bogdanova wrote:
> Broker log content also needs to be replicated from OE 1:1 which it's not currently.
Pleas... Constantin Asofiei

09:04 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> > > Also that way I won't have to rename CentralLogger to SideLogger.
> >
> > I don't see why this is needed reg... Greg Shah

09:00 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Constantin, you asked before about the appserver/broker logs and what is happening with them.
With #5753 there wil... Galya B

08:59 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> > Also that way I won't have to rename CentralLogger to SideLogger.
>
> I don't see why this i... Galya B

08:57 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> This Status, API, IDE thing - isn't it like any cloud logging + IDE plugin? Any cloud logging has an API and a Java... Greg Shah

03:56 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

This Status, API, IDE thing - isn't it like any cloud logging + IDE plugin? Any cloud logging has an API and a Java l... Galya B

03/21/2023

10:03 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> Replace all CentralLogger references only in the seven conversion / tool directories and don't care about dependenc... Greg Shah

10:03 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> > It should hide the runtime vs devtime decision from the caller.
> Are the two distinguishable? Is there a differ... Greg Shah

04:38 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> Anything in these directories is conversion or dev tool related:
> ... Galya B

03:23 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> It should hide the runtime vs devtime decision from the caller.
Are the two distinguishable? Is ... Galya B

03/20/2023

12:10 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Anything in these directories is conversion or dev tool related:... Greg Shah

11:04 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

@Preprocessor@ is not in @com.goldencode.p2j.convert@. So let me get back to my initial question.
Greg Shah wrote:... Galya B

10:55 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Call it @Status@. Greg Shah

10:54 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

The interface and implementations should live inside @com.goldencode.p2j.convert@. Greg Shah

10:53 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Use the minimum necessary to replace the current calls. Greg Shah

10:52 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> No, I don't think so. The two APIs may look similar now but they will not look that way later.
... Galya B

10:51 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> > Think about the case of IDE integration which needs to show a list of errors and link back to the location of the... Greg Shah

10:46 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

@CentralLogger@ is just an interface. Its various implementations may or may not have anything in common.
As far as ... Galya B

10:43 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> Think about the case of IDE integration which needs to show a list of errors and link back to the... Galya B

10:39 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

The API is not really about logging. It is about recording the details of the conversion/tools processing in a manne... Greg Shah

10:34 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> Anything that ever gets used at conversion time would use this API instead of direct usage of @Ce... Galya B

10:31 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Galya Bogdanova wrote:
> I'm not able to determine in depth which files are part only of the conversion tool and whi... Greg Shah

10:30 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> But that's the issue, it already does,
What do you mean by "it already does"? In your changes?
> since bein... Greg Shah

10:30 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

I'm not able to determine in depth which files are part only of the conversion tool and which are shared with other r... Galya B

10:28 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> I prefer that the API be the main entry point for the tooling and @CentralLogger@ only used in on... Galya B

10:27 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Galya Bogdanova wrote:
> I guess the API will be backed by a new DB table?
Not at this time. For now, the conver... Greg Shah

10:26 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

I prefer that the API be the main entry point for the tooling and @CentralLogger@ only used in one implementation of ... Greg Shah

10:26 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

I guess the API will be backed by a new DB table? Galya B

10:23 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

We can mark the tools entry points to run CentralLogger with a new mode that writes to the API and we'll have to repl... Galya B

10:20 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

I think we should implement a version of the #7180 API and switch all the conversion-tooling to use it. We can insta... Greg Shah

10:19 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> It is completely common code.
Then my changes - replacing System.err will change the output in b... Galya B

10:17 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Galya Bogdanova wrote:
> If runtime conversion and tools conversion don't share any classes, then minding my own ref... Greg Shah

10:17 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

> Do we need exceptions in the GWT front-end of admin/client saved in the central log file or leave them show up only... Greg Shah

10:15 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

If runtime conversion and tools conversion don't share any classes, then minding my own refactoring will be easy. Oth... Galya B

10:14 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Galya Bogdanova wrote:
> About the interactive tools - I've marked in the [[internal-documentation:Logs#section-42|t... Greg Shah

10:13 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Greg Shah wrote:
> Please note that the conversion output for running the tools outside of runtime is the more impor... Galya B

10:11 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Galya Bogdanova wrote:
> Also @ext/sheet/build.gradle@ uses compile time the fwd build folder @../../build/classes@,... Greg Shah

10:10 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Galya Bogdanova wrote:
> @com.goldencode.p2j.preproc.Preprocessor@ supports cmd line options for writing out, err an... Greg Shah

08:44 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Attention! %{color:red}⚠% Replacing @System.err@ in the project will affect the content of the @-err@ and @-war... Galya B

03:46 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Do we need exceptions in the GWT front-end of admin/client saved in the central log file or leave them show up only i... Galya B

03/16/2023

11:46 AM Bug #5701 (Closed): logfile names for -O outputToFile use the spawner pid instead of the Java (FW...

Feedback status is for when the task is blocked needing information from the Author and/or a customer. Leave it in T... Greg Shah

11:42 AM Bug #5701 (Feedback): logfile names for -O outputToFile use the spawner pid instead of the Java (...

Galya B

04:58 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

5701b is merged to trunk under r14506 -and works fine, but there are regression issues with the previous revision r14... Galya B

03/14/2023

06:24 PM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

Please rebase 5701b from trunk rev 14505. Then if it passes your basic tests, you can merge to trunk. Greg Shah

03/13/2023

12:16 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

There is a problem: There are 100 entry points in the code. Most of them have System.out and System.err. If System.er... Galya B

11:36 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

About the interactive tools - I've marked in the [[internal-documentation:Logs#section-42|table]] the classes using S... Galya B

09:34 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Also @ext/sheet/build.gradle@ uses compile time the fwd build folder @../../build/classes@, so I guess p2j.jar is in ... Galya B