[jira] [Commented] (OFBIZ-12896) Fix trunk documentation generation in BuidBot
[
https://issues.apache.org/jira/browse/OFBIZ-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816147#comment-17816147
]
Jacques Le Roux commented on OFBIZ-12896:
-
Olivier did really a great job, thanks [~holivier]!
> Fix trunk documentation generation in BuidBot
> -
>
> Key: OFBIZ-12896
> URL: https://issues.apache.org/jira/browse/OFBIZ-12896
> Project: OFBiz
> Issue Type: Bug
> Components: asciidoc, BuildBot
>Affects Versions: Upcoming Branch
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: Upcoming Branch
>
>
> It's a weird mess, maybe I miss something :/
> Some same includes links that works well in 18.12 branch don't in trunk. I
> thought it could be due to java version but not even since I see that in the
> 18.12 build:
> {quote}
> To honour the JVM settings for this build a new JVM will be forked. Please
> consider using the daemon:
> [https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will
> be stopped at the end of the build stopping after processing
> > Task :deleteOfbizDocumentation
> > Task :generateOfbizDocumentation
> unsupported Java version "11", defaulting to 1.7
> BUILD SUCCESSFUL in 55s
> 2 actionable tasks: 2 executed
> {quote}
> I'll not backport in 22.01 since it's supposed to abandonned in favour of a
> future 24.xx branch
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-12896) Fix trunk documentation generation in BuidBot
[
https://issues.apache.org/jira/browse/OFBIZ-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816139#comment-17816139
]
ASF subversion and git services commented on OFBIZ-12896:
-
Commit 26e7e96cb280a695a3981b2be0369d62991379e8 in ofbiz-framework's branch
refs/heads/trunk from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=26e7e96cb2 ]
Fixed: Fix trunk documentation generation in BuidBot (OFBIZ-12896)
Remains only
> Task :generateOfbizDocumentation
INFOS: possible invalid reference: _step_5_employee_leaves
INFOS: possible invalid reference: _step_1_pay_grade_and_salary_step
INFOS: possible invalid reference: _step_4_employee_associated_benefits
INFOS: possible invalid reference: _tutorial_employment_and_salary
It seems those are indeed missing...
> Fix trunk documentation generation in BuidBot
> -
>
> Key: OFBIZ-12896
> URL: https://issues.apache.org/jira/browse/OFBIZ-12896
> Project: OFBiz
> Issue Type: Bug
> Components: asciidoc, BuildBot
>Affects Versions: Upcoming Branch
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: Upcoming Branch
>
>
> It's a weird mess, maybe I miss something :/
> Some same includes links that works well in 18.12 branch don't in trunk. I
> thought it could be due to java version but not even since I see that in the
> 18.12 build:
> {quote}
> To honour the JVM settings for this build a new JVM will be forked. Please
> consider using the daemon:
> [https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will
> be stopped at the end of the build stopping after processing
> > Task :deleteOfbizDocumentation
> > Task :generateOfbizDocumentation
> unsupported Java version "11", defaulting to 1.7
> BUILD SUCCESSFUL in 55s
> 2 actionable tasks: 2 executed
> {quote}
> I'll not backport in 22.01 since it's supposed to abandonned in favour of a
> future 24.xx branch
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (OFBIZ-12898) In Solr fixe NPE in FieldLengthFeature with non-stored/missing fields.
[ https://issues.apache.org/jira/browse/OFBIZ-12898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-12898. --- Resolution: Fixed > In Solr fixe NPE in FieldLengthFeature with non-stored/missing fields. > -- > > Key: OFBIZ-12898 > URL: https://issues.apache.org/jira/browse/OFBIZ-12898 > Project: OFBiz > Issue Type: Bug > Components: lucene, solr >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > It's not a CVE, not backport needed. For details, see > https://lucene.apache.org/core/8_11_3/changes/Changes.html > https://lucene.apache.org/core/8_11_3/changes/Changes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12898) In Solr fixe NPE in FieldLengthFeature with non-stored/missing fields.
[ https://issues.apache.org/jira/browse/OFBIZ-12898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816129#comment-17816129 ] ASF subversion and git services commented on OFBIZ-12898: - Commit 0c6e278ac8a763d77898b5c8b5a412dde8c5 in ofbiz-plugins's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=0c6e278ac ] Fixed: In Solr fixe NPE in FieldLengthFeature with non-stored/missing fields. (OFBIZ-12898) It's not a CVE, not backport needed. For details, see https://lucene.apache.org/core/8_11_3/changes/Changes.html https://lucene.apache.org/core/8_11_3/changes/Changes.html > In Solr fixe NPE in FieldLengthFeature with non-stored/missing fields. > -- > > Key: OFBIZ-12898 > URL: https://issues.apache.org/jira/browse/OFBIZ-12898 > Project: OFBiz > Issue Type: Bug > Components: lucene, solr >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > It's not a CVE, not backport needed. For details, see > https://lucene.apache.org/core/8_11_3/changes/Changes.html > https://lucene.apache.org/core/8_11_3/changes/Changes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12898) In Solr fixe NPE in FieldLengthFeature with non-stored/missing fields.
Jacques Le Roux created OFBIZ-12898: --- Summary: In Solr fixe NPE in FieldLengthFeature with non-stored/missing fields. Key: OFBIZ-12898 URL: https://issues.apache.org/jira/browse/OFBIZ-12898 Project: OFBiz Issue Type: Bug Components: lucene, solr Affects Versions: Upcoming Branch Reporter: Jacques Le Roux Assignee: Jacques Le Roux Fix For: Upcoming Branch It's not a CVE, not backport needed. For details, see https://lucene.apache.org/core/8_11_3/changes/Changes.html https://lucene.apache.org/core/8_11_3/changes/Changes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12896) Fix trunk documentation generation in BuidBot
[
https://issues.apache.org/jira/browse/OFBIZ-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816127#comment-17816127
]
Jacques Le Roux commented on OFBIZ-12896:
-
https://docs.asciidoctor.org/asciidoc/latest/directives/include/#include-resolution
explain all about include paths resolution.
TL;DR anyway in BB it must be an "absolute" path (relative to OFBiz root dir)
> Fix trunk documentation generation in BuidBot
> -
>
> Key: OFBIZ-12896
> URL: https://issues.apache.org/jira/browse/OFBIZ-12896
> Project: OFBiz
> Issue Type: Bug
> Components: asciidoc, BuildBot
>Affects Versions: Upcoming Branch
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: Upcoming Branch
>
>
> It's a weird mess, maybe I miss something :/
> Some same includes links that works well in 18.12 branch don't in trunk. I
> thought it could be due to java version but not even since I see that in the
> 18.12 build:
> {quote}
> To honour the JVM settings for this build a new JVM will be forked. Please
> consider using the daemon:
> [https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will
> be stopped at the end of the build stopping after processing
> > Task :deleteOfbizDocumentation
> > Task :generateOfbizDocumentation
> unsupported Java version "11", defaulting to 1.7
> BUILD SUCCESSFUL in 55s
> 2 actionable tasks: 2 executed
> {quote}
> I'll not backport in 22.01 since it's supposed to abandonned in favour of a
> future 24.xx branch
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-12897) Rework the log4j2.xml configuration to limit the number of log files generated
[ https://issues.apache.org/jira/browse/OFBIZ-12897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816126#comment-17816126 ] Jacques Le Roux edited comment on OFBIZ-12897 at 2/9/24 4:06 PM: - At bottom of OFBIZ-12889, I wrote: bq. Thanks Daniel, I remember having done that before for a project. I'll see if I have still a gist of it... But I remember now that was before lo4j2 (ie with lo4j), so it's no usable. I'll though doublecheck... was (Author: jacques.le.roux): At bottom of OFBIZ-12889, I wrote: bq. Thanks Daniel, I remember having done that before for a project. I'll see if I have still a gist of it... But that was before lo4j2 (ie with lo4j), so it's no usable. I'll though doublecheck... > Rework the log4j2.xml configuration to limit the number of log files generated > -- > > Key: OFBIZ-12897 > URL: https://issues.apache.org/jira/browse/OFBIZ-12897 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Upcoming Branch, 18.12.11 >Reporter: Daniel Watford >Priority: Minor > > File lo4j2.xml configure log file rolling, but it does not appear to function > as perhaps intended. > Log file rolling is configured to keep up to 10 log files. But the log file > naming convention appears to cause a maximum of 10 logs files to be kept for > each day. > Rework the log4j2.xml configuration file to ensure that only 10 log files are > kept (for each appender) regardless of the date. > Also, a limit of 1MB is quite small these days, particularly as text editors > can easily search through larger files without a noticeable performance > penalty (YMMV). I recommend raising the log file size limit to 10MB as this > would keep more log entries around without a corresponding increase in the > number of file. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12897) Rework the log4j2.xml configuration to limit the number of log files generated
[ https://issues.apache.org/jira/browse/OFBIZ-12897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816126#comment-17816126 ] Jacques Le Roux commented on OFBIZ-12897: - At bottom of OFBIZ-12889, I wrote: bq. Thanks Daniel, I remember having done that before for a project. I'll see if I have still a gist of it... But that was before lo4j2 (ie with lo4j), so it's no usable. I'll though doublecheck... > Rework the log4j2.xml configuration to limit the number of log files generated > -- > > Key: OFBIZ-12897 > URL: https://issues.apache.org/jira/browse/OFBIZ-12897 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Upcoming Branch, 18.12.11 >Reporter: Daniel Watford >Priority: Minor > > File lo4j2.xml configure log file rolling, but it does not appear to function > as perhaps intended. > Log file rolling is configured to keep up to 10 log files. But the log file > naming convention appears to cause a maximum of 10 logs files to be kept for > each day. > Rework the log4j2.xml configuration file to ensure that only 10 log files are > kept (for each appender) regardless of the date. > Also, a limit of 1MB is quite small these days, particularly as text editors > can easily search through larger files without a noticeable performance > penalty (YMMV). I recommend raising the log file size limit to 10MB as this > would keep more log entries around without a corresponding increase in the > number of file. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12896) Fix trunk documentation generation in BuidBot
[
https://issues.apache.org/jira/browse/OFBIZ-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816103#comment-17816103
]
Jacques Le Roux commented on OFBIZ-12896:
-
Actually next files seems OK. Anyway they will be replaced.
> Fix trunk documentation generation in BuidBot
> -
>
> Key: OFBIZ-12896
> URL: https://issues.apache.org/jira/browse/OFBIZ-12896
> Project: OFBiz
> Issue Type: Bug
> Components: asciidoc, BuildBot
>Affects Versions: Upcoming Branch
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: Upcoming Branch
>
>
> It's a weird mess, maybe I miss something :/
> Some same includes links that works well in 18.12 branch don't in trunk. I
> thought it could be due to java version but not even since I see that in the
> 18.12 build:
> {quote}
> To honour the JVM settings for this build a new JVM will be forked. Please
> consider using the daemon:
> [https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will
> be stopped at the end of the build stopping after processing
> > Task :deleteOfbizDocumentation
> > Task :generateOfbizDocumentation
> unsupported Java version "11", defaulting to 1.7
> BUILD SUCCESSFUL in 55s
> 2 actionable tasks: 2 executed
> {quote}
> I'll not backport in 22.01 since it's supposed to abandonned in favour of a
> future 24.xx branch
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-12889) Expose runtime/logs directory to host for demo docker containers
[ https://issues.apache.org/jira/browse/OFBIZ-12889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816058#comment-17816058 ] Jacques Le Roux commented on OFBIZ-12889: - Thanks Daniel, I remember having done that before for a project. I'll see if I have still a gist of it... > Expose runtime/logs directory to host for demo docker containers > > > Key: OFBIZ-12889 > URL: https://issues.apache.org/jira/browse/OFBIZ-12889 > Project: OFBiz > Issue Type: Task > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Minor > > OFBiz writes to various log files at path runtime/logs. These log files are > not easily* accessible by administrators on hosts running OFBiz in docker > containers, such as the project's demo sites. > Modify the demo sites configuration and the example docker configurations to > make the various OFBiz logs accessible to administrators. > > * The log files can currently be accessed by exec'ing processes in a running > container, but this is cumbersome and not something we should expect system > administrators to do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12896) Fix trunk documentation generation in BuidBot
[
https://issues.apache.org/jira/browse/OFBIZ-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816055#comment-17816055
]
ASF subversion and git services commented on OFBIZ-12896:
-
Commit 0b7145f86cfb81c9887f4e3ffb7b8e9053433f4d in ofbiz-framework's branch
refs/heads/trunk from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=0b7145f86c ]
Fixed: Fix trunk documentation generation in BuidBot (OFBIZ-12896)
It's difficult because the rendering depends of the renderer tool
For instance I use the AsciiDoctor Eclipse plugin and it works with
the relative path from the current file (documentation_guidelines.adoc)
include::resource/source.java[]
but not with the "absolute" path (relative to OFBiz root dir)
include::docs/asciidoc/resource/source.java[]
I trust the later will be ok in BB;
let's see before changing also user-manual.adoc
> Fix trunk documentation generation in BuidBot
> -
>
> Key: OFBIZ-12896
> URL: https://issues.apache.org/jira/browse/OFBIZ-12896
> Project: OFBiz
> Issue Type: Bug
> Components: asciidoc, BuildBot
>Affects Versions: Upcoming Branch
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: Upcoming Branch
>
>
> It's a weird mess, maybe I miss something :/
> Some same includes links that works well in 18.12 branch don't in trunk. I
> thought it could be due to java version but not even since I see that in the
> 18.12 build:
> {quote}
> To honour the JVM settings for this build a new JVM will be forked. Please
> consider using the daemon:
> [https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will
> be stopped at the end of the build stopping after processing
> > Task :deleteOfbizDocumentation
> > Task :generateOfbizDocumentation
> unsupported Java version "11", defaulting to 1.7
> BUILD SUCCESSFUL in 55s
> 2 actionable tasks: 2 executed
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OFBIZ-12896) Fix trunk documentation generation in BuidBot
[
https://issues.apache.org/jira/browse/OFBIZ-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-12896:
Description:
It's a weird mess, maybe I miss something :/
Some same includes links that works well in 18.12 branch don't in trunk. I
thought it could be due to java version but not even since I see that in the
18.12 build:
{quote}
To honour the JVM settings for this build a new JVM will be forked. Please
consider using the daemon:
[https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will be
stopped at the end of the build stopping after processing
> Task :deleteOfbizDocumentation
> Task :generateOfbizDocumentation
unsupported Java version "11", defaulting to 1.7
BUILD SUCCESSFUL in 55s
2 actionable tasks: 2 executed
{quote}
I'll not backport in 22.01 since it's supposed to abandonned in favour of a
future 24.xx branch
was:
It's a weird mess, maybe I miss something :/
Some same includes links that works well in 18.12 branch don't in trunk. I
thought it could be due to java version but not even since I see that in the
18.12 build:
{quote}
To honour the JVM settings for this build a new JVM will be forked. Please
consider using the daemon:
[https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will be
stopped at the end of the build stopping after processing
> Task :deleteOfbizDocumentation
> Task :generateOfbizDocumentation
unsupported Java version "11", defaulting to 1.7
BUILD SUCCESSFUL in 55s
2 actionable tasks: 2 executed
{quote}
> Fix trunk documentation generation in BuidBot
> -
>
> Key: OFBIZ-12896
> URL: https://issues.apache.org/jira/browse/OFBIZ-12896
> Project: OFBiz
> Issue Type: Bug
> Components: asciidoc, BuildBot
>Affects Versions: Upcoming Branch
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: Upcoming Branch
>
>
> It's a weird mess, maybe I miss something :/
> Some same includes links that works well in 18.12 branch don't in trunk. I
> thought it could be due to java version but not even since I see that in the
> 18.12 build:
> {quote}
> To honour the JVM settings for this build a new JVM will be forked. Please
> consider using the daemon:
> [https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will
> be stopped at the end of the build stopping after processing
> > Task :deleteOfbizDocumentation
> > Task :generateOfbizDocumentation
> unsupported Java version "11", defaulting to 1.7
> BUILD SUCCESSFUL in 55s
> 2 actionable tasks: 2 executed
> {quote}
> I'll not backport in 22.01 since it's supposed to abandonned in favour of a
> future 24.xx branch
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OFBIZ-12896) Fix trunk documentation generation in BuidBot
[
https://issues.apache.org/jira/browse/OFBIZ-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-12896:
Description:
It's a weird mess, maybe I miss something :/
Some same includes links that works well in 18.12 branch don't in trunk. I
thought it could be due to java version but not even since I see that in the
18.12 build:
{quote}
To honour the JVM settings for this build a new JVM will be forked. Please
consider using the daemon:
[https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will be
stopped at the end of the build stopping after processing
> Task :deleteOfbizDocumentation
> Task :generateOfbizDocumentation
unsupported Java version "11", defaulting to 1.7
BUILD SUCCESSFUL in 55s
2 actionable tasks: 2 executed
{quote}
was:
It's a weird mess, maybe I miss something :/
Some same includes links that works well in 18.12 branch don't in trunk. I
thought it could be due to java version but not even since I see that in the
18.12 build:
{quote}
To honour the JVM settings for this build a new JVM will be forked. Please
consider using the daemon:
[https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will be
stopped at the end of the build stopping after processing
> Task :deleteOfbizDocumentation
> Task :generateOfbizDocumentation
unsupported Java version "11", defaulting to 1.7
BUILD SUCCESSFUL in 55s
2 actionable tasks: 2 executed
{quote}
> Fix trunk documentation generation in BuidBot
> -
>
> Key: OFBIZ-12896
> URL: https://issues.apache.org/jira/browse/OFBIZ-12896
> Project: OFBiz
> Issue Type: Bug
> Components: asciidoc, BuildBot
>Affects Versions: Upcoming Branch
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: Upcoming Branch
>
>
> It's a weird mess, maybe I miss something :/
> Some same includes links that works well in 18.12 branch don't in trunk. I
> thought it could be due to java version but not even since I see that in the
> 18.12 build:
> {quote}
> To honour the JVM settings for this build a new JVM will be forked. Please
> consider using the daemon:
> [https://docs.gradle.org/5.0-rc-5/userguide/gradle_daemon.html].Daemon will
> be stopped at the end of the build stopping after processing
> > Task :deleteOfbizDocumentation
> > Task :generateOfbizDocumentation
> unsupported Java version "11", defaulting to 1.7
> BUILD SUCCESSFUL in 55s
> 2 actionable tasks: 2 executed
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OFBIZ-12897) Rework the log4j2.xml configuration to limit the number of log files generated
Daniel Watford created OFBIZ-12897: -- Summary: Rework the log4j2.xml configuration to limit the number of log files generated Key: OFBIZ-12897 URL: https://issues.apache.org/jira/browse/OFBIZ-12897 Project: OFBiz Issue Type: Task Components: framework Affects Versions: 18.12.11, Upcoming Branch Reporter: Daniel Watford File lo4j2.xml configure log file rolling, but it does not appear to function as perhaps intended. Log file rolling is configured to keep up to 10 log files. But the log file naming convention appears to cause a maximum of 10 logs files to be kept for each day. Rework the log4j2.xml configuration file to ensure that only 10 log files are kept (for each appender) regardless of the date. Also, a limit of 1MB is quite small these days, particularly as text editors can easily search through larger files without a noticeable performance penalty (YMMV). I recommend raising the log file size limit to 10MB as this would keep more log entries around without a corresponding increase in the number of file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12889) Expose runtime/logs directory to host for demo docker containers
[ https://issues.apache.org/jira/browse/OFBIZ-12889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816024#comment-17816024 ] Daniel Watford commented on OFBIZ-12889: OFBIZ-12897 created to address log file rolling. I'm happy for someone else to pick up that ticket if they get to it sooner than me. > Expose runtime/logs directory to host for demo docker containers > > > Key: OFBIZ-12889 > URL: https://issues.apache.org/jira/browse/OFBIZ-12889 > Project: OFBiz > Issue Type: Task > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Minor > > OFBiz writes to various log files at path runtime/logs. These log files are > not easily* accessible by administrators on hosts running OFBiz in docker > containers, such as the project's demo sites. > Modify the demo sites configuration and the example docker configurations to > make the various OFBiz logs accessible to administrators. > > * The log files can currently be accessed by exec'ing processes in a running > container, but this is cumbersome and not something we should expect system > administrators to do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12889) Expose runtime/logs directory to host for demo docker containers
[ https://issues.apache.org/jira/browse/OFBIZ-12889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816023#comment-17816023 ] Daniel Watford commented on OFBIZ-12889: I was looking at the same thing myself this morning. I would like to change the rolling log file appender's configuration in log4j2.xml to rework log rolling and prevent the number of files growing without bound. I thought I would make relevant changes under a different ticket though, particularly since I would like to change the default logging configuration rather than anything to do with our use of docker. > Expose runtime/logs directory to host for demo docker containers > > > Key: OFBIZ-12889 > URL: https://issues.apache.org/jira/browse/OFBIZ-12889 > Project: OFBiz > Issue Type: Task > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Minor > > OFBiz writes to various log files at path runtime/logs. These log files are > not easily* accessible by administrators on hosts running OFBiz in docker > containers, such as the project's demo sites. > Modify the demo sites configuration and the example docker configurations to > make the various OFBiz logs accessible to administrators. > > * The log files can currently be accessed by exec'ing processes in a running > container, but this is cumbersome and not something we should expect system > administrators to do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Improved: show MainActionMenu in Party - LoggedInUser screen (OFBIZ-12895) [ofbiz-framework]
sonarcloud[bot] commented on PR #691: URL: https://github.com/apache/ofbiz-framework/pull/691#issuecomment-1935559511 ## [](https://sonarcloud.io/dashboard?id=apache_ofbiz-framework=691) **Quality Gate passed** Issues  [0 New issues](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=691=false=true) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-framework=691=false=true)  No data about Coverage  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=691=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_ofbiz-framework=691) -- 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: notifications-unsubscr...@ofbiz.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Improved: show MainActionMenu in Party - LoggedInUser screen (OFBIZ-12895) [ofbiz-framework]
PierreSmits opened a new pull request, #691: URL: https://github.com/apache/ofbiz-framework/pull/691 Currently the ListLoggedInUsers screen in VisitScreens.xml does not show the MainActionMenu of the party component. For a consistent user experience this should be. Modified: VisitScreens.xml - added decorator-section 'pre-body' having MainActionMenu to screen ListLoggedInUser -- 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: notifications-unsubscr...@ofbiz.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (OFBIZ-12889) Expose runtime/logs directory to host for demo docker containers
[ https://issues.apache.org/jira/browse/OFBIZ-12889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815972#comment-17815972 ] Jacques Le Roux commented on OFBIZ-12889: - BTW, I see 3 days logs, is there a kind of rotation or maybe simply only the logs of the day? > Expose runtime/logs directory to host for demo docker containers > > > Key: OFBIZ-12889 > URL: https://issues.apache.org/jira/browse/OFBIZ-12889 > Project: OFBiz > Issue Type: Task > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Minor > > OFBiz writes to various log files at path runtime/logs. These log files are > not easily* accessible by administrators on hosts running OFBiz in docker > containers, such as the project's demo sites. > Modify the demo sites configuration and the example docker configurations to > make the various OFBiz logs accessible to administrators. > > * The log files can currently be accessed by exec'ing processes in a running > container, but this is cumbersome and not something we should expect system > administrators to do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12889) Expose runtime/logs directory to host for demo docker containers
[ https://issues.apache.org/jira/browse/OFBIZ-12889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815970#comment-17815970 ] Jacques Le Roux commented on OFBIZ-12889: - Great, thanks Daniel! > Expose runtime/logs directory to host for demo docker containers > > > Key: OFBIZ-12889 > URL: https://issues.apache.org/jira/browse/OFBIZ-12889 > Project: OFBiz > Issue Type: Task > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Minor > > OFBiz writes to various log files at path runtime/logs. These log files are > not easily* accessible by administrators on hosts running OFBiz in docker > containers, such as the project's demo sites. > Modify the demo sites configuration and the example docker configurations to > make the various OFBiz logs accessible to administrators. > > * The log files can currently be accessed by exec'ing processes in a running > container, but this is cumbersome and not something we should expect system > administrators to do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12892) Screen Classifications in Party should not show create trigger to user with only VIEW permission
[ https://issues.apache.org/jira/browse/OFBIZ-12892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815961#comment-17815961 ] Pierre Smits commented on OFBIZ-12892: -- Thanks [~jleroux], for your assistance in getting this into the codebase. > Screen Classifications in Party should not show create trigger to user with > only VIEW permission > > > Key: OFBIZ-12892 > URL: https://issues.apache.org/jira/browse/OFBIZ-12892 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Upcoming Branch >Reporter: Pierre Smits >Priority: Major > > When accessing > [https://demo-trunk.ofbiz.apache.org/partymgr/control/showclassgroups] as a > user with only VIEW permissions (e.g. userId = auditor) the action trigger to > create a new Party Classification Group is shown. > This should not be visible to such a user as it leads to an undesired effect > and diminished user experience. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12889) Expose runtime/logs directory to host for demo docker containers
[ https://issues.apache.org/jira/browse/OFBIZ-12889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Watford closed OFBIZ-12889. -- Resolution: Implemented > Expose runtime/logs directory to host for demo docker containers > > > Key: OFBIZ-12889 > URL: https://issues.apache.org/jira/browse/OFBIZ-12889 > Project: OFBiz > Issue Type: Task > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Minor > > OFBiz writes to various log files at path runtime/logs. These log files are > not easily* accessible by administrators on hosts running OFBiz in docker > containers, such as the project's demo sites. > Modify the demo sites configuration and the example docker configurations to > make the various OFBiz logs accessible to administrators. > > * The log files can currently be accessed by exec'ing processes in a running > container, but this is cumbersome and not something we should expect system > administrators to do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Improved: display Run Service forms with dynamic fields (OFBIZ-12869) [ofbiz-framework]
JacquesLeRoux commented on PR #675: URL: https://github.com/apache/ofbiz-framework/pull/675#issuecomment-1935481853 Hi @mleila37 , Same seems like a good PR to push :) -- 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: notifications-unsubscr...@ofbiz.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
