Re: [PR] Improved: CONTENT- Move from hard-coded menu location to parameterized (OFBIZ-12978) [ofbiz-plugins]
sonarcloud[bot] commented on PR #124: URL: https://github.com/apache/ofbiz-plugins/pull/124#issuecomment-2119320358 ## [](https://sonarcloud.io/dashboard?id=apache_ofbiz-plugins=124) **Quality Gate passed** Issues  [0 New issues](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=124=false=true)  [0 Accepted issues](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=124=WONTFIX) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-plugins=124=false=true)  No data about Coverage  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_ofbiz-plugins=124=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_ofbiz-plugins=124) -- 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-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=17847693#comment-17847693 ] Jacques Le Roux commented on OFBIZ-12897: - Hi Daniel, Sorry, about next demos I see still the *2024*.log files. The next demo is not of great interest at the moment, but will be when we will create the 24.xx branch. TIA, again not a hurry. BTW how do you get access to the 166536 user? > 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 >Assignee: Daniel Watford >Priority: Minor > Fix For: Upcoming Branch, 18.12.13 > > > 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] [Updated] (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:all-tabpanel ] Jacques Le Roux updated OFBIZ-12897: Fix Version/s: Upcoming Branch 18.12.13 > 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 >Assignee: Daniel Watford >Priority: Minor > Fix For: Upcoming Branch, 18.12.13 > > > 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] [Closed] (OFBIZ-13096) Implement log rolling for access logs
[ https://issues.apache.org/jira/browse/OFBIZ-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-13096. --- Assignee: Jacques Le Roux Resolution: Fixed Hi Daniel, It was done with OFBIZ-13073. I also fixed the name with OFBIZ-13089 Thanks to care :) > Implement log rolling for access logs > - > > Key: OFBIZ-13096 > URL: https://issues.apache.org/jira/browse/OFBIZ-13096 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > Similar to OFBIZ-12897, identify the component/configuration that affects > generation of access logs in the demo sites and introduce log rolling. > OFBIZ-12897 introduced log rolling behaviour for the ofbiz and error logs, > but has not effect on the generation of access logs. > Suitable log rolling of the access logs should be introduced so that we can > avoid needing to manually clean up these logs. In particular, this will help > with the maintenance of the demo sites. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Improved: CONTENT- Move from hard-coded menu location to parameterized (OFBIZ-12978) [ofbiz-plugins]
sonarcloud[bot] commented on PR #124: URL: https://github.com/apache/ofbiz-plugins/pull/124#issuecomment-2119230620 ## [](https://sonarcloud.io/dashboard?id=apache_ofbiz-plugins=124) **Quality Gate passed** Issues  [0 New issues](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=124=false=true)  [0 Accepted issues](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=124=WONTFIX) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-plugins=124=false=true)  No data about Coverage  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_ofbiz-plugins=124=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_ofbiz-plugins=124) -- 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: CONTENT- Move from hard-coded menu location to parameterized (OFBIZ-12978) [ofbiz-plugins]
PierreSmits opened a new pull request, #124: URL: https://github.com/apache/ofbiz-plugins/pull/124 modified: web.xml (lucene) - added: context-param for content menus -- 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] [Closed] (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:all-tabpanel ] Daniel Watford closed OFBIZ-12897. -- Resolution: Implemented > 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 >Assignee: 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=17847668#comment-17847668 ] Daniel Watford commented on OFBIZ-12897: Done > 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 >Assignee: 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-13096) Implement log rolling for access logs
[ https://issues.apache.org/jira/browse/OFBIZ-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847667#comment-17847667 ] Daniel Watford commented on OFBIZ-13096: After taking another look, this may have already been implemented. Currently there are 31 access log files on the ofbiz-vm1 host for the demo-trunk and demo-stable sites. I'll check in a few days to see if the number of log files has remained static. > Implement log rolling for access logs > - > > Key: OFBIZ-13096 > URL: https://issues.apache.org/jira/browse/OFBIZ-13096 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Priority: Minor > Fix For: Upcoming Branch > > > Similar to OFBIZ-12897, identify the component/configuration that affects > generation of access logs in the demo sites and introduce log rolling. > OFBIZ-12897 introduced log rolling behaviour for the ofbiz and error logs, > but has not effect on the generation of access logs. > Suitable log rolling of the access logs should be introduced so that we can > avoid needing to manually clean up these logs. In particular, this will help > with the maintenance of the demo sites. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13096) Implement log rolling for access logs
Daniel Watford created OFBIZ-13096: -- Summary: Implement log rolling for access logs Key: OFBIZ-13096 URL: https://issues.apache.org/jira/browse/OFBIZ-13096 Project: OFBiz Issue Type: Improvement Affects Versions: Upcoming Branch Reporter: Daniel Watford Fix For: Upcoming Branch Similar to OFBIZ-12897, identify the component/configuration that affects generation of access logs in the demo sites and introduce log rolling. OFBIZ-12897 introduced log rolling behaviour for the ofbiz and error logs, but has not effect on the generation of access logs. Suitable log rolling of the access logs should be introduced so that we can avoid needing to manually clean up these logs. In particular, this will help with the maintenance of the demo sites. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13048) createPlugin - improve templates
[ https://issues.apache.org/jira/browse/OFBIZ-13048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-13048: - Description: With the parameterization of the menu location, improvements to the createPlugin templates are warranted. Replacing minilang folder with script folder, to ensure developers have a place to have their non-compiled script files (groovy and others). Removing non English labels, as in coding English is the internationally used language (and more particarly within the ASF communities). was: With the parameterization of the menu location, improvements to the createPlugin templates are warranted. replacing mining with script folder, to ensure developers have a place to have their non-compiled script files (groovy and others). Removing non English labels, as in coding English is the internationally used language (and more particarly within the ASF communities). > createPlugin - improve templates > > > Key: OFBIZ-13048 > URL: https://issues.apache.org/jira/browse/OFBIZ-13048 > Project: OFBiz > Issue Type: Improvement > Components: framework >Reporter: Pierre Smits >Priority: Major > Labels: development > > With the parameterization of the menu location, improvements to the > createPlugin templates are warranted. > Replacing minilang folder with script folder, to ensure developers have a > place to have their non-compiled script files (groovy and others). > Removing non English labels, as in coding English is the internationally used > language (and more particarly within the ASF communities). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13048) createPlugin - improve templates
[ https://issues.apache.org/jira/browse/OFBIZ-13048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-13048: - Description: With the parameterization of the menu location, improvements to the createPlugin templates are warranted. replacing mining with script folder, to ensure developers have a place to have their non-compiled script files (groovy and others). Removing non English labels, as in coding English is the internationally used language (and more particarly within the ASF communities). was:With the parameterization of the menu location, improvements to the createPlugin templates are warranted. > createPlugin - improve templates > > > Key: OFBIZ-13048 > URL: https://issues.apache.org/jira/browse/OFBIZ-13048 > Project: OFBiz > Issue Type: Improvement > Components: framework >Reporter: Pierre Smits >Priority: Major > Labels: development > > With the parameterization of the menu location, improvements to the > createPlugin templates are warranted. > replacing mining with script folder, to ensure developers have a place to > have their non-compiled script files (groovy and others). > Removing non English labels, as in coding English is the internationally used > language (and more particarly within the ASF communities). -- 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=17847633#comment-17847633 ] Jacques Le Roux edited comment on OFBIZ-12897 at 5/19/24 11:28 AM: --- Hi Daniel, Before we close here, I had a look at cleaning the demos logs. Nothing is needed in stable but next and trunk have a bunch of now old \*2024\*.log files. I tried to remove them as ofbizdocker user but got a "Permission denied" error. They have been set has 166536 user properties. IIRW this is Docker. Could you remove them, maybe using docker-image.yaml or related? TIA was (Author: jacques.le.roux): Hi Daniel, Before we close here, I had a look at cleaning the demos logs. Nothing is needed in stable but next and trunk have a bunch of now old *2024*.log files. I tried to remove them as ofbizdocker user but got a "Permission denied" error. They have been set has 166536 user properties. IIRW this is Docker. Could you remove them, maybe using docker-image.yaml or related? TIA > 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 >Assignee: 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=17847665#comment-17847665 ] Jacques Le Roux commented on OFBIZ-12897: - Thanks Daniel, no hurry. > 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 >Assignee: 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-13095) The non ASCII language in UiLabels.xml are not correctly handled during plugin creation
[ https://issues.apache.org/jira/browse/OFBIZ-13095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847664#comment-17847664 ] Jacques Le Roux commented on OFBIZ-13095: - Yes thanks, I remembered something about that but was unable to remember where. Anyway it's done now. It's committed but not yet pushed for other good reasons. BTW, in such cases a good explanation in the Jira description can help... Will see later... > The non ASCII language in UiLabels.xml are not correctly handled during > plugin creation > --- > > Key: OFBIZ-13095 > URL: https://issues.apache.org/jira/browse/OFBIZ-13095 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: 18.12.14 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > > You get this error: > 2024-05-19 09:52:41,314 |jsse-nio-8443-exec-3 |UtilProperties > |W| XML file for locale could not be loaded. > org.xml.sax.SAXParseException: Invalid byte 3 of 3-byte UTF-8 sequence. > When removing ZH labels it works. We should keep only English languages or > amend the createPlugin Gradle task. In this issue I'll remove ZH labels and > put a comment as documentation about that for developers in > framework/resources/templates/UiLabels.xml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13095) The non ASCII language in UiLabels.xml are not correctly handled during plugin creation
[ https://issues.apache.org/jira/browse/OFBIZ-13095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847660#comment-17847660 ] Pierre Smits commented on OFBIZ-13095: -- Hi [~jleroux], With pull request 778 re OFBIZ-13048, I already removed the ZH labels. > The non ASCII language in UiLabels.xml are not correctly handled during > plugin creation > --- > > Key: OFBIZ-13095 > URL: https://issues.apache.org/jira/browse/OFBIZ-13095 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: 18.12.14 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > > You get this error: > 2024-05-19 09:52:41,314 |jsse-nio-8443-exec-3 |UtilProperties > |W| XML file for locale could not be loaded. > org.xml.sax.SAXParseException: Invalid byte 3 of 3-byte UTF-8 sequence. > When removing ZH labels it works. We should keep only English languages or > amend the createPlugin Gradle task. In this issue I'll remove ZH labels and > put a comment as documentation about that for developers in > framework/resources/templates/UiLabels.xml -- 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=17847659#comment-17847659 ] Daniel Watford commented on OFBIZ-12897: Hi [~jleroux] - I'll take care of clearing the older log files. > 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 >Assignee: 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-13080) Duplicate main menu button after plugin creation
[ https://issues.apache.org/jira/browse/OFBIZ-13080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847650#comment-17847650 ] Jacques Le Roux commented on OFBIZ-13080: - Thans Sebastian, I did not test in 18.12, I guess it's due to recent changes in trunk. > Duplicate main menu button after plugin creation > > > Key: OFBIZ-13080 > URL: https://issues.apache.org/jira/browse/OFBIZ-13080 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Sebastian Tschikin >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > After creating a plugin with 'gradlew createPlugin -PpluginId=myplugin' there > is a duplicate main menu button in the backend menu of the new plugin. > I am going to provide a fix for that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-13080) Duplicate main menu button after plugin creation
[ https://issues.apache.org/jira/browse/OFBIZ-13080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-13080. --- Resolution: Fixed > Duplicate main menu button after plugin creation > > > Key: OFBIZ-13080 > URL: https://issues.apache.org/jira/browse/OFBIZ-13080 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Sebastian Tschikin >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > After creating a plugin with 'gradlew createPlugin -PpluginId=myplugin' there > is a duplicate main menu button in the backend menu of the new plugin. > I am going to provide a fix for that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-13080) Duplicate main menu button after plugin creation
[ https://issues.apache.org/jira/browse/OFBIZ-13080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-13080: --- Component/s: Gradle Fix Version/s: Upcoming Branch Affects Version/s: Upcoming Branch Assignee: Jacques Le Roux (was: Sebastian Tschikin) > Duplicate main menu button after plugin creation > > > Key: OFBIZ-13080 > URL: https://issues.apache.org/jira/browse/OFBIZ-13080 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Sebastian Tschikin >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > After creating a plugin with 'gradlew createPlugin -PpluginId=myplugin' there > is a duplicate main menu button in the backend menu of the new plugin. > I am going to provide a fix for that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13080) Duplicate main menu button after plugin creation
[ https://issues.apache.org/jira/browse/OFBIZ-13080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847649#comment-17847649 ] ASF subversion and git services commented on OFBIZ-13080: - Commit 3aba9e9dc7b1e67a417bc3d7111d4b38706bf6c4 in ofbiz-framework's branch refs/heads/trunk from Sebastian Tschikin [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=3aba9e9dc7 ] Fixed: Duplicate main menu button after plugin creation (OFBIZ-13080) (#794) The 'main' menu-item is no longer necessary as there is a default main menu button for every plugin. > Duplicate main menu button after plugin creation > > > Key: OFBIZ-13080 > URL: https://issues.apache.org/jira/browse/OFBIZ-13080 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sebastian Tschikin >Assignee: Sebastian Tschikin >Priority: Minor > > After creating a plugin with 'gradlew createPlugin -PpluginId=myplugin' there > is a duplicate main menu button in the backend menu of the new plugin. > I am going to provide a fix for that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Fixed: Duplicate main menu button after plugin creation (OFBIZ-13080) [ofbiz-framework]
JacquesLeRoux merged PR #794: URL: https://github.com/apache/ofbiz-framework/pull/794 -- 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] [Updated] (OFBIZ-13080) Duplicate main menu button after plugin creation
[ https://issues.apache.org/jira/browse/OFBIZ-13080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-13080: Parent: OFBIZ-13094 Issue Type: Sub-task (was: Bug) > Duplicate main menu button after plugin creation > > > Key: OFBIZ-13080 > URL: https://issues.apache.org/jira/browse/OFBIZ-13080 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sebastian Tschikin >Assignee: Sebastian Tschikin >Priority: Minor > > After creating a plugin with 'gradlew createPlugin -PpluginId=myplugin' there > is a duplicate main menu button in the backend menu of the new plugin. > I am going to provide a fix for that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13095) The non ASCII language in UiLabels.xml are not correctly handled during plugin creation
[ https://issues.apache.org/jira/browse/OFBIZ-13095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-13095: Summary: The non ASCII language in UiLabels.xml are not correctly handled during plugin creation (was: The non ASCII language in UiLabels.xml are not correctly handled during creation) > The non ASCII language in UiLabels.xml are not correctly handled during > plugin creation > --- > > Key: OFBIZ-13095 > URL: https://issues.apache.org/jira/browse/OFBIZ-13095 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: 18.12.14 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > > You get this error: > 2024-05-19 09:52:41,314 |jsse-nio-8443-exec-3 |UtilProperties > |W| XML file for locale could not be loaded. > org.xml.sax.SAXParseException: Invalid byte 3 of 3-byte UTF-8 sequence. > When removing ZH labels it works. We should keep only English languages or > amend the createPlugin Gradle task. In this issue I'll remove ZH labels and > put a comment as documentation about that for developers in > framework/resources/templates/UiLabels.xml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13095) The non ASCII language in UiLabels.xml are not correctly handled during creation
Jacques Le Roux created OFBIZ-13095: --- Summary: The non ASCII language in UiLabels.xml are not correctly handled during creation Key: OFBIZ-13095 URL: https://issues.apache.org/jira/browse/OFBIZ-13095 Project: OFBiz Issue Type: Sub-task Components: Gradle Affects Versions: 18.12.14 Reporter: Jacques Le Roux Assignee: Jacques Le Roux You get this error: 2024-05-19 09:52:41,314 |jsse-nio-8443-exec-3 |UtilProperties |W| XML file for locale could not be loaded. org.xml.sax.SAXParseException: Invalid byte 3 of 3-byte UTF-8 sequence. When removing ZH labels it works. We should keep only English languages or amend the createPlugin Gradle task. In this issue I'll remove ZH labels and put a comment as documentation about that for developers in framework/resources/templates/UiLabels.xml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13094) Errors after creating a plugin
[ https://issues.apache.org/jira/browse/OFBIZ-13094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-13094: Description: This is a generic task to handle the multiple errors that happen after creating a plugin and trying to use it (was: This is an generic task to handle the multiple errors that happen after creating a plugin and trying to use it) > Errors after creating a plugin > -- > > Key: OFBIZ-13094 > URL: https://issues.apache.org/jira/browse/OFBIZ-13094 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: 18.12.14 >Reporter: Jacques Le Roux >Priority: Major > > This is a generic task to handle the multiple errors that happen after > creating a plugin and trying to use it -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13094) Errors after creating a plugin
Jacques Le Roux created OFBIZ-13094: --- Summary: Errors after creating a plugin Key: OFBIZ-13094 URL: https://issues.apache.org/jira/browse/OFBIZ-13094 Project: OFBiz Issue Type: Bug Components: Gradle Affects Versions: 18.12.14 Reporter: Jacques Le Roux This is an generic task to handle the multiple errors that happen after creating a plugin and trying to use it -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Improved: Manufacturing-Main page (OFBIZ-13053) [ofbiz-framework]
sonarcloud[bot] commented on PR #784: URL: https://github.com/apache/ofbiz-framework/pull/784#issuecomment-2119138667 ## [](https://sonarcloud.io/dashboard?id=apache_ofbiz-framework=784) **Quality Gate passed** Issues  [0 New issues](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=784=false=true)  [0 Accepted issues](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=784=WONTFIX) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-framework=784=false=true)  No data about Coverage  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=784=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_ofbiz-framework=784) -- 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] [Closed] (OFBIZ-8290) Disentangle unused Accounting labels
[ https://issues.apache.org/jira/browse/OFBIZ-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-8290. -- Fix Version/s: Upcoming Branch Resolution: Implemented > Disentangle unused Accounting labels > > > Key: OFBIZ-8290 > URL: https://issues.apache.org/jira/browse/OFBIZ-8290 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk, Upcoming Branch >Reporter: Pierre Smits >Priority: Trivial > Labels: labels, refactoring > Fix For: Upcoming Branch > > Attachments: OFBIZ-8290-AccountingUiLabels.xml.patch > > > Disentanglement of unused labels from the accounting component makes the > component better. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-10565) Clean Labels
[ https://issues.apache.org/jira/browse/OFBIZ-10565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10565. --- Fix Version/s: Upcoming Branch Assignee: Jacques Le Roux Resolution: Implemented > Clean Labels > > > Key: OFBIZ-10565 > URL: https://issues.apache.org/jira/browse/OFBIZ-10565 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk, Upcoming Branch >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Minor > Labels: cleanup > Fix For: Upcoming Branch > > Time Spent: 20m > Remaining Estimate: 0h > > Labels get added when code changes are introduced. But it can also happen > that the (unused) label is forgotten while doing code clean-ups, refactoring > of the change before a patch submitted or a commit is executed. Or that > progressing insight leads to have the code change go into a different > component. Or that they came from a pre-ASF era and never got applied. > This is an umbrella ticket, capturing (future) sub-tasks and should be > considered an ongoing effort to keep the code base as concise as possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-8290) Disentangle unused Accounting labels
[ https://issues.apache.org/jira/browse/OFBIZ-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-8290: -- Assignee: Jacques Le Roux > Disentangle unused Accounting labels > > > Key: OFBIZ-8290 > URL: https://issues.apache.org/jira/browse/OFBIZ-8290 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk, Upcoming Branch >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Labels: labels, refactoring > Fix For: Upcoming Branch > > Attachments: OFBIZ-8290-AccountingUiLabels.xml.patch > > > Disentanglement of unused labels from the accounting component makes the > component better. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-8154) Some labels are considered not used by the Label Manager
[ https://issues.apache.org/jira/browse/OFBIZ-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-8154. -- Fix Version/s: Upcoming Branch Resolution: Implemented > Some labels are considered not used by the Label Manager > > > Key: OFBIZ-8154 > URL: https://issues.apache.org/jira/browse/OFBIZ-8154 > Project: OFBiz > Issue Type: Sub-task > Components: framework/webtools >Affects Versions: Trunk, Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > As I said in my r1759457 commit comment: > bq. We have 5237 "Not Used Labels". I wondered if they were all real, I just > checked some an indeed, they were not used. But there are also a huge bunch > of *.description.* labels which certainly make sense. I'll remove them from > the "Only Not Used Labels" result in another Jira I'll create > Here is the promised Jira -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-8154) Some labels are considered not used by the Label Manager
[ https://issues.apache.org/jira/browse/OFBIZ-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-8154: -- Assignee: Jacques Le Roux > Some labels are considered not used by the Label Manager > > > Key: OFBIZ-8154 > URL: https://issues.apache.org/jira/browse/OFBIZ-8154 > Project: OFBiz > Issue Type: Sub-task > Components: framework/webtools >Affects Versions: Trunk, Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > > As I said in my r1759457 commit comment: > bq. We have 5237 "Not Used Labels". I wondered if they were all real, I just > checked some an indeed, they were not used. But there are also a huge bunch > of *.description.* labels which certainly make sense. I'll remove them from > the "Only Not Used Labels" result in another Jira I'll create > Here is the promised Jira -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12951) CommonExt - Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-12951. --- Resolution: Implemented > CommonExt - Move from hard-code menu location to parameterized > -- > > Key: OFBIZ-12951 > URL: https://issues.apache.org/jira/browse/OFBIZ-12951 > Project: OFBiz > Issue Type: Sub-task > Components: commonext >Affects Versions: Upcoming Branch >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > Attachments: Screenshot 2024-05-05 at 20.32.11.png, Screenshot > 2024-05-13 at 12.18.38.png > > > Move the menu location in the various commonest screens from hard-coded to > parameterized. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12951) CommonExt - Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847635#comment-17847635 ] ASF subversion and git services commented on OFBIZ-12951: - Commit 24d42f3be2913b33543c77ae8323dc5a98d9cbe7 in ofbiz-framework's branch refs/heads/trunk from Pierre Smits [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=24d42f3be2 ] Improved: CommonExt - Move from hard-code menu location to parameterized (OFBIZ-12951) (#795) * Improved: CommonExt - Move from hard-code menu location to parameterized (OFBIZ-12951) ofbizsetup uses profile screens from partymgr. modified web.xml - added profileMenuLocation * OFBIZ-12951 Fix dependency on party ofbizsetup is dependent on party elements modified: commonext - web.xml: added new context-param for createNewParty menu modified: party - web.xml: added new context-param for createNewParty menu - PartyScreens.xml: changed location createNewParty menu reference * Improved: CommonExt - Move from hard-code menu location to parameterized (OFBIZ-12951) modified: Menus.xml - added MainActionMenu extending MainActionMenu in PartyMenus.xml > CommonExt - Move from hard-code menu location to parameterized > -- > > Key: OFBIZ-12951 > URL: https://issues.apache.org/jira/browse/OFBIZ-12951 > Project: OFBiz > Issue Type: Sub-task > Components: commonext >Affects Versions: Upcoming Branch >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > Attachments: Screenshot 2024-05-05 at 20.32.11.png, Screenshot > 2024-05-13 at 12.18.38.png > > > Move the menu location in the various commonest screens from hard-coded to > parameterized. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Improved: CommonExt - Move from hard-code menu location to parameterized (OFBIZ-12951) [ofbiz-framework]
JacquesLeRoux merged PR #795: URL: https://github.com/apache/ofbiz-framework/pull/795 -- 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-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=17847633#comment-17847633 ] Jacques Le Roux commented on OFBIZ-12897: - Hi Daniel, Before we close here, I had a look at cleaning the demos logs. Nothing is needed in stable but next and trunk have a bunch of now old *2024*.log files. I tried to remove them as ofbizdocker user but got a "Permission denied" error. They have been set has 166536 user properties. IIRW this is Docker. Could you remove them, maybe using docker-image.yaml or related? TIA > 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 >Assignee: 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] [Updated] (OFBIZ-12391) Trustworthy OFBiz - audit capabilities
[ https://issues.apache.org/jira/browse/OFBIZ-12391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-12391: Fix Version/s: Upcoming Branch > Trustworthy OFBiz - audit capabilities > -- > > Key: OFBIZ-12391 > URL: https://issues.apache.org/jira/browse/OFBIZ-12391 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS, framework/entity >Affects Versions: Trunk, Upcoming Branch >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: audit, entity, investigation, mvp, trust, usability > Fix For: Upcoming Branch > > > When potential adopters want to use OFBiz as their primary solution for > business critical ERP (and related) processes, they (or at least their > auditors) want to be sure that they can see: > # who created the record in the underlying rdbms, > # when that record was created, > # who was the last one to modify the record > # when the modification happened. > Currently out of the 800+ entities defined in the various entity model files, > only a fraction of the entities have fields defined for > * createdDate (23) > * createdByUserLogin (30) > * lastModifiedDate (24) > * lastModifiedByUserLogin (29) > which means that for crucial entities (for a business) in OFBiz entities > records can be created and changed (for nefarious reasons) without auditors > and other investigators being able to state anything regarding the above 4 > points. > Currently there are over 600 entity-auto services invoking 'create', and > approximately the same amount of services that invoke 'update', that could > automatically set the fields listed above. However it is not done, because > these have not been defined. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12391) Trustworthy OFBiz - audit capabilities
[ https://issues.apache.org/jira/browse/OFBIZ-12391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-12391. --- Resolution: Implemented > Trustworthy OFBiz - audit capabilities > -- > > Key: OFBIZ-12391 > URL: https://issues.apache.org/jira/browse/OFBIZ-12391 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS, framework/entity >Affects Versions: Trunk, Upcoming Branch >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: audit, entity, investigation, mvp, trust, usability > > When potential adopters want to use OFBiz as their primary solution for > business critical ERP (and related) processes, they (or at least their > auditors) want to be sure that they can see: > # who created the record in the underlying rdbms, > # when that record was created, > # who was the last one to modify the record > # when the modification happened. > Currently out of the 800+ entities defined in the various entity model files, > only a fraction of the entities have fields defined for > * createdDate (23) > * createdByUserLogin (30) > * lastModifiedDate (24) > * lastModifiedByUserLogin (29) > which means that for crucial entities (for a business) in OFBiz entities > records can be created and changed (for nefarious reasons) without auditors > and other investigators being able to state anything regarding the above 4 > points. > Currently there are over 600 entity-auto services invoking 'create', and > approximately the same amount of services that invoke 'update', that could > automatically set the fields listed above. However it is not done, because > these have not been defined. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-10476) Remove Compdoc functionality from content manager
[ https://issues.apache.org/jira/browse/OFBIZ-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847632#comment-17847632 ] Jacques Le Roux commented on OFBIZ-10476: - Hi Michael, Any chances for 18.12 before we release 18.12.14? > Remove Compdoc functionality from content manager > - > > Key: OFBIZ-10476 > URL: https://issues.apache.org/jira/browse/OFBIZ-10476 > Project: OFBiz > Issue Type: Improvement > Components: content >Affects Versions: Release Branch 18.12, Trunk, Upcoming Branch >Reporter: Dennis Balkir >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > > While creating a theme and looking for not correctly styled elements I came > across "some" not functional links and buttons in Compdoc. > This module seems not to be finished or working properly, because most of the > times, the buttons inside the appbar produce errors or just empty pages. > Even when searching for existing elements and then clicking on them to > examine or edit them will mostly create an error (example: go to compdoc, > search for template child, click edit on some random found element -> error). > Sometimes the menu which is included inside the appbar, mostly the menu > called "tree", need the contentId for the buttons to work. > Including this menu while creating a new entry will result in every button > not working and throwing an error, except the edit button, which will produce > a completely empty page. > Those things appear all over the module, trying some button or clicking some > link resulted in an error screen more than it resulted in something actually > working. > This should either be fixed or removed, if this doesn't has a real purpose at > all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-5170) Profiling OFBiz
[ https://issues.apache.org/jira/browse/OFBIZ-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-5170. -- Resolution: Implemented > Profiling OFBiz > --- > > Key: OFBIZ-5170 > URL: https://issues.apache.org/jira/browse/OFBIZ-5170 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk, Upcoming Branch >Reporter: Adrian Crum >Priority: Minor > Attachments: HotSpotSettings.PNG, HotSpots_Rev_1464779.csv > > > I will be using this issue to share the things I learn while profiling OFBiz > to study the impact of removing Javolution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
