[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300756#comment-17300756 ] Jacques Le Roux commented on OFBIZ-12192: - Hi Michael, I'll handle the Windows case, quite easy :) > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300432#comment-17300432 ] Jacopo Cappellato commented on OFBIZ-12192: --- One solution for 17.12 that seems to work is to modify init-wrapper.sh to get the release 4.5.1 of the wrapper jar from GitHub's Gradle; the script should not grab the properties file because the one from GitHub contains an URL that doesn't work; instead we should just keep the properties file we already have in our repo (that already references 4.5.1) > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-12191) Bug preventing proper explosion of BOM containing virtual nodes
[
https://issues.apache.org/jira/browse/OFBIZ-12191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pawan Verma reassigned OFBIZ-12191:
---
Assignee: Pawan Verma
> Bug preventing proper explosion of BOM containing virtual nodes
> ---
>
> Key: OFBIZ-12191
> URL: https://issues.apache.org/jira/browse/OFBIZ-12191
> Project: OFBiz
> Issue Type: Bug
> Components: manufacturing
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Pawan Verma
>Priority: Major
> Attachments: OFBIZ-12191.patch, OFBIZ-12191_sample-data.xml,
> image-2021-02-27-18-37-47-422.png
>
>
> I tried the following use case. We configured BOM for the virtual product
> whose nodes can also be virtual.
>
> {code:java}
> // Product To Be produced
> PROD_MANUF_1 (Virtual Product)
> - PROD_MANUF_11 (Variant)
> - PROD_MANUF_12 (Variant)
>
> // Raw Material
> RAW_MAT_1 (Virtual)
> - RAW_MAT_11 (Variant)
> - RAW_MAT_12 (Variant)
>
> RAW_MAT_2 (Standard)
> // BOM
> PROD_MANUF_1-> RAW_MAT_1
> -> RAW_MAT_2
> PROD_MANUF_11 -> RAW_MAT_11 -> 2 Qty
> -> RAW_MAT_2 -> 2 Qty
>
>
> PROD_MANUF_12 -> RAW_MAT_12 -> 3 Qty
> -> RAW_MAT_2 -> 2 Qty {code}
> Now let say we want to manufacture 10qty of PROD_MANUF_12. To my
> expectations, the requirement generated should be like
> - To produce 10qty for PROD_MANUF_12 we will need
> - 30qty of RAW_MAT_12
> - 20qty of RAW_MAT_2
> But the result for MRP and BOM simulation is incorrect. Please refer to the
> screenshot.
> !image-2021-02-27-18-37-47-422.png!
> _I am also attaching sample data to test._
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12153) Error in deleting Financial Account
[ https://issues.apache.org/jira/browse/OFBIZ-12153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-12153: Attachment: OFBIZ-12153.patch > Error in deleting Financial Account > --- > > Key: OFBIZ-12153 > URL: https://issues.apache.org/jira/browse/OFBIZ-12153 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Lalit Dashora >Assignee: sourabh jain >Priority: Major > Attachments: FinAccountDelete.png, OFBIZ-12153.patch, > OFBIZ-12153.patch, OFBIZ-12153.patch, OFBIZ-12153.patch, OFBIZ-12153.patch, > OFBIZ-12153.patch > > > 1. Navigate to URL: accounting/control/FindFinAccount > 2. Click on Find button. List of fin account will be displayed. > 3. Click on delete button near available balance column. > The Following Errors Occurred: > Error doing entity-auto operation for entity FinAccount in service > deleteFinAccount: org.apache.ofbiz.entity.GenericEntityException: > org.apache.ofbiz.entity.GenericDataSourceException: Exception while deleting > the following entity: > [GenericEntity:FinAccount][finAccountId,SC_CHECKING(java.lang.String)] (SQL > Exception while executing the following:null (DELETE on table 'FIN_ACCOUNT' > caused a violation of foreign key constraint 'FINACT_STTS_FNA' for key > (SC_CHECKING). The statement has been rolled back.)) (Exception while > deleting the following entity: > [GenericEntity:FinAccount][finAccountId,SC_CHECKING(java.lang.String)] (SQL > Exception while executing the following:null (DELETE on table 'FIN_ACCOUNT' > caused a violation of foreign key constraint 'FINACT_STTS_FNA' for key > (SC_CHECKING). The statement has been rolled back.))) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12153) Error in deleting Financial Account
[ https://issues.apache.org/jira/browse/OFBIZ-12153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300421#comment-17300421 ] Pawan Verma commented on OFBIZ-12153: - Hi [~jleroux] Here is the patch for R17 and R18, Could you please have a look! [^OFBIZ-12153.patch] > Error in deleting Financial Account > --- > > Key: OFBIZ-12153 > URL: https://issues.apache.org/jira/browse/OFBIZ-12153 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Lalit Dashora >Assignee: sourabh jain >Priority: Major > Attachments: FinAccountDelete.png, OFBIZ-12153.patch, > OFBIZ-12153.patch, OFBIZ-12153.patch, OFBIZ-12153.patch, OFBIZ-12153.patch, > OFBIZ-12153.patch > > > 1. Navigate to URL: accounting/control/FindFinAccount > 2. Click on Find button. List of fin account will be displayed. > 3. Click on delete button near available balance column. > The Following Errors Occurred: > Error doing entity-auto operation for entity FinAccount in service > deleteFinAccount: org.apache.ofbiz.entity.GenericEntityException: > org.apache.ofbiz.entity.GenericDataSourceException: Exception while deleting > the following entity: > [GenericEntity:FinAccount][finAccountId,SC_CHECKING(java.lang.String)] (SQL > Exception while executing the following:null (DELETE on table 'FIN_ACCOUNT' > caused a violation of foreign key constraint 'FINACT_STTS_FNA' for key > (SC_CHECKING). The statement has been rolled back.)) (Exception while > deleting the following entity: > [GenericEntity:FinAccount][finAccountId,SC_CHECKING(java.lang.String)] (SQL > Exception while executing the following:null (DELETE on table 'FIN_ACCOUNT' > caused a violation of foreign key constraint 'FINACT_STTS_FNA' for key > (SC_CHECKING). The statement has been rolled back.))) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300305#comment-17300305 ] Jacques Le Roux edited comment on OFBIZ-12192 at 3/12/21, 1:42 PM: --- BTW, after reading about FREEMARKER-124 at https://freemarker.apache.org/docs/versions_2_3_30.html bq. Made the default filtering of class members more restrictive (when you are using BeansWrapper, or its subclasses like DefaultObjectWrapper). This is not strictly backward compatible, but unlikely to break any real-world applications; see src/main/resources/freemarker/ext/beans/DefaultMemberAccessPolicy-rules to see what was changed. This change was made for security reasons, but the default behavior will never be safe enough if untrusted users will edit templates; see in the FAQ. In the unlikely case this change breaks your application, then you can still use the old behavior by setting the memberAccessPolicy property of the object wrapper to LegacyDefaultMemberAccessPolicy.INSTANCE. I send this to the dev ML: https://markmail.org/message/r5yyhis5qwk53akn bq. After fixing this issue, I believe we should use Freemarker 2.3.31 in all supported branches because of possible (low but who knows...) security issues fixed since 2.3.30. What do you think? was (Author: jacques.le.roux): BTW, after reading about FREEMARKER-124 at https://freemarker.apache.org/docs/versions_2_3_30.html bq. Made the default filtering of class members more restrictive (when you are using BeansWrapper, or its subclasses like DefaultObjectWrapper). This is not strictly backward compatible, but unlikely to break any real-world applications; see src/main/resources/freemarker/ext/beans/DefaultMemberAccessPolicy-rules to see what was changed. This change was made for security reasons, but the default behavior will never be safe enough if untrusted users will edit templates; see in the FAQ. In the unlikely case this change breaks your application, then you can still use the old behavior by setting the memberAccessPolicy property of the object wrapper to LegacyDefaultMemberAccessPolicy.INSTANCE. I send this to the dev ML: https://markmail.org/message/r5yyhis5qwk53akn bq. After fixing this issue, I believe we should use Freemarker 2.3.31 in all supported branches because of possible (low but who knows...) security issues fixed since 2.3.30. What do you think? > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300305#comment-17300305 ] Jacques Le Roux commented on OFBIZ-12192: - BTW, after reading about FREEMARKER-124 at https://freemarker.apache.org/docs/versions_2_3_30.html bq. Made the default filtering of class members more restrictive (when you are using BeansWrapper, or its subclasses like DefaultObjectWrapper). This is not strictly backward compatible, but unlikely to break any real-world applications; see src/main/resources/freemarker/ext/beans/DefaultMemberAccessPolicy-rules to see what was changed. This change was made for security reasons, but the default behavior will never be safe enough if untrusted users will edit templates; see in the FAQ. In the unlikely case this change breaks your application, then you can still use the old behavior by setting the memberAccessPolicy property of the object wrapper to LegacyDefaultMemberAccessPolicy.INSTANCE. I send this to the dev ML: https://markmail.org/message/r5yyhis5qwk53akn bq. After fixing this issue, I believe we should use Freemarker 2.3.31 in all supported branches because of possible (low but who knows...) security issues fixed since 2.3.30. What do you think? > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300296#comment-17300296 ] Jacques Le Roux commented on OFBIZ-12192: - [~jacopoc]: Yes, I did LEGAL-564 for the peace of mind. I see indeed no reason to legally prevent to download files that can be reached by anyone. BTW why would Infra be concerned? We (OFBiz users using scripts) would only download from GH after all. Would this have an impact on GitBox? [~mbrohl]: OK > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300290#comment-17300290 ] Michael Brohl commented on OFBIZ-12192: --- [~jleroux] sure, I think I will work on it later today so please notify your findings here, thanks. > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300287#comment-17300287 ] Jacopo Cappellato commented on OFBIZ-12192: --- [~jleroux] : I don't think that downloading from GitHub should concern Legal; the only issue may be related to infra (e.g. scalability issue if number of downloads is too large for GitHub), but for 17.12 we should be fine. [~mbrohl] : I am also testing the init script with the backup url and I am facing some issues that I am trying to address (in my free time); we can sync up here if needed > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300271#comment-17300271 ] Jacques Le Roux commented on OFBIZ-12192: - Great, I can do that > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300256#comment-17300256 ] Michael Brohl commented on OFBIZ-12192: --- > Sounds like a plan :) Will you handle the Windows part? I can change the files but need someone to test, I am on Mac OS. > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300254#comment-17300254 ] Jacques Le Roux commented on OFBIZ-12192: - I suppose there will be no issues with LEGAL-564. I can modify https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz for this part > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300250#comment-17300250 ] Jacques Le Roux edited comment on OFBIZ-12192 at 3/12/21, 11:45 AM: Sounds like a plan :) Will you handle the Windows part? was (Author: jacques.le.roux): Sounds like a plan :) > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300250#comment-17300250 ] Jacques Le Roux commented on OFBIZ-12192: - Sounds like a plan :) > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300249#comment-17300249 ] Michael Brohl edited comment on OFBIZ-12192 at 3/12/21, 11:43 AM: -- I can then prepare this for 17.12 today, if noone beats me to it ;) was (Author: mbrohl): I can then prepare this for 17.12 today. > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300248#comment-17300248 ] Michael Brohl commented on OFBIZ-12192: --- Ah, great, then I'll propose to change the init scripts to only use the Gradle / GitHub urls without backup. What do you think? > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300249#comment-17300249 ] Michael Brohl commented on OFBIZ-12192: --- I can then prepare this for 17.12 today. > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12171) Handling the JCenter shutdown
[ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300245#comment-17300245 ] Michael Brohl commented on OFBIZ-12171: --- I also need to modify the file checksums accordingly for all branches. > Handling the JCenter shutdown > - > > Key: OFBIZ-12171 > URL: https://issues.apache.org/jira/browse/OFBIZ-12171 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: 18.12.01, Upcoming Branch, 17.12.06 > > Attachments: OFBIZ-12171-1712-README.patch > > > Citing Taher's message at [2]: > Hello Everyone, > > I received emails and checked resources [1] that seem to confirm JCenter from > JFrog is going down and that the last day of operation for the repository is > going to be May 1st 2021. > > This is a big deal as many running instances will crash unless updated, so > not only do future versions of OFBiz need to adapt, but also existing > installations. > > I'm not sure how to best handle this? Especially for production instances out > there on older versions of OFBiz. Maybe one solution is to host the existing > libraries in some temporary location or try to migrate them to MavenCentral > ... Whatever is the solution I think we should make a fast move. > > [1] > [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter] > > [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure] > [2] > [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12192) Replace Bintray by a new place to upload the Gradle Wrapper
[ https://issues.apache.org/jira/browse/OFBIZ-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300244#comment-17300244 ] Jacopo Cappellato commented on OFBIZ-12192: --- The init-gradle-wrapper.sh (*nix version) already supports the download (as a backup url) from gradle on github (see variable GRADLE_WRAPPER_URI_BACKUP) If it works, we could just leave with it at least in the old release branch 17.12 > Replace Bintray by a new place to upload the Gradle Wrapper > --- > > Key: OFBIZ-12192 > URL: https://issues.apache.org/jira/browse/OFBIZ-12192 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: 18.12.01, Trunk, 17.12.06 >Reporter: Jacques Le Roux >Priority: Blocker > > We got an issue with Bintray and jcenter : > [https://markmail.org/message/hal4od7xeoig6xfw] > The jcenter aspect is now fixed with OFBIZ-12171 (actually jcenter will allow > download until February 1st 2022) > With our need to upload the Gradle Wrapper we have though still an issue with > Bintray: [https://markmail.org/message/74u6wsldx3ykzqiv] > The problem is once we release a package the scripts at > [https://github.com/apache/ofbiz-framework/tree/trunk/gradle] are freezed. So > people using these scripts will not be able to download the related Gradle > Wrapper versions. > So we need to replace Bintray by another place to upload the different > versions of the Gradle Wrapper. All supported OFBiz versions are concerned. > Note: I have already put > [https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray] > in Wiki Attic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12171) Handling the JCenter shutdown
[ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300238#comment-17300238 ] Jacques Le Roux commented on OFBIZ-12171: - Hi Jacopo, After OFBIZ-12192, I have created LEGAL-564 to ask if we could use Github to replace Bintray to download the Gradle Wrapper. > Handling the JCenter shutdown > - > > Key: OFBIZ-12171 > URL: https://issues.apache.org/jira/browse/OFBIZ-12171 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: 18.12.01, Upcoming Branch, 17.12.06 > > Attachments: OFBIZ-12171-1712-README.patch > > > Citing Taher's message at [2]: > Hello Everyone, > > I received emails and checked resources [1] that seem to confirm JCenter from > JFrog is going down and that the last day of operation for the repository is > going to be May 1st 2021. > > This is a big deal as many running instances will crash unless updated, so > not only do future versions of OFBiz need to adapt, but also existing > installations. > > I'm not sure how to best handle this? Especially for production instances out > there on older versions of OFBiz. Maybe one solution is to host the existing > libraries in some temporary location or try to migrate them to MavenCentral > ... Whatever is the solution I think we should make a fast move. > > [1] > [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter] > > [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure] > [2] > [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12171) Handling the JCenter shutdown
[ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300236#comment-17300236 ] Michael Brohl commented on OFBIZ-12171: --- Thanks for reporting this, [~jacopoc] ! I think we should not only change the version but also change the download link to something other than dl.bintray.com because of the shutdown. I'll work on this over the weekend. > Handling the JCenter shutdown > - > > Key: OFBIZ-12171 > URL: https://issues.apache.org/jira/browse/OFBIZ-12171 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: 18.12.01, Upcoming Branch, 17.12.06 > > Attachments: OFBIZ-12171-1712-README.patch > > > Citing Taher's message at [2]: > Hello Everyone, > > I received emails and checked resources [1] that seem to confirm JCenter from > JFrog is going down and that the last day of operation for the repository is > going to be May 1st 2021. > > This is a big deal as many running instances will crash unless updated, so > not only do future versions of OFBiz need to adapt, but also existing > installations. > > I'm not sure how to best handle this? Especially for production instances out > there on older versions of OFBiz. Maybe one solution is to host the existing > libraries in some temporary location or try to migrate them to MavenCentral > ... Whatever is the solution I think we should make a fast move. > > [1] > [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter] > > [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure] > [2] > [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12177) Possibly currency display bug in "Find Invoices"
[ https://issues.apache.org/jira/browse/OFBIZ-12177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300225#comment-17300225 ] Jacques Le Roux commented on OFBIZ-12177: - Hi Priya, I agree with Suraj and I tested locally. Please go ahead with your 1st commit, don't forget to backport :) > Possibly currency display bug in "Find Invoices" > > > Key: OFBIZ-12177 > URL: https://issues.apache.org/jira/browse/OFBIZ-12177 > Project: OFBiz > Issue Type: Bug >Reporter: Andrei Stan >Assignee: Priya Sharma >Priority: Minor > Attachments: Captură de ecran de la 2021-02-15 17-31-06.png, Captură > de ecran de la 2021-02-15 17-33-34.png, OFBIZ-12177.patch > > > h4. - in the page with the "Invoices List", the numbers are wrong for "Total: > EUR 820.2773" of "demo11001". > h4. Steps to generate: > Open https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices > - see that invoice "demo11001" has the Total of *EUR* 820.2773. > - click on the Invoice id "demo11001" > - if you look at payments, we can see that a payment of *EUR* 543.23 was made > and applied. > * in the invoice Overview we can see the correct currency $ is with the > amount of 820.2773 -> > https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=demo10001 > I think the bug is this: > * it should display USD 820.2773 or *EUR* 543.23 in the "Invoices List (find > invoieces)" page ?!? > * in the project file > "../applications/datamodel/data/demo/AccountingDemoData.xml" you > * can see the converting factor: > ** > > 00:00:00.0"conversionFactor="1.5"/> => *EUR 543.23 = $ 820.2773* > > * as an enhancement for the payments in other currencies i think it would be > usefull to display the Total amount of the invoice with it's currency > alogside the amount of total payments in other currency, applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12171) Handling the JCenter shutdown
[ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300220#comment-17300220 ] Jacopo Cappellato commented on OFBIZ-12171: --- Hi [~mbrohl], and thanks for all the work! I am preparing the release files for 17.12.06 and testing the build process for 17.12 and I am finding some issues introduced with [https://github.com/apache/ofbiz-framework/commit/d6c6330b390a96bdf6a7d65573117b693455c685] The problem is that, in the release files, we have to remove the jar file in gradle/wrapper; at build time, as described in the README file, the jar file is downloaded using the script gradle/init-gradle-wrapper This script actually downloads the jar file and the properties file from [https://dl.bintray.com/apacheofbiz/GradleWrapper/] Currently in init-gradle-wrapper we still have the version 3.2.1; we should also update (I guess) the new properties file to bintray. I may find other issues (I am still testing) but for now I ma reporting the one above. > Handling the JCenter shutdown > - > > Key: OFBIZ-12171 > URL: https://issues.apache.org/jira/browse/OFBIZ-12171 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: 18.12.01, Upcoming Branch, 17.12.06 > > Attachments: OFBIZ-12171-1712-README.patch > > > Citing Taher's message at [2]: > Hello Everyone, > > I received emails and checked resources [1] that seem to confirm JCenter from > JFrog is going down and that the last day of operation for the repository is > going to be May 1st 2021. > > This is a big deal as many running instances will crash unless updated, so > not only do future versions of OFBiz need to adapt, but also existing > installations. > > I'm not sure how to best handle this? Especially for production instances out > there on older versions of OFBiz. Maybe one solution is to host the existing > libraries in some temporary location or try to migrate them to MavenCentral > ... Whatever is the solution I think we should make a fast move. > > [1] > [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter] > > [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure] > [2] > [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-9863) Use Labels in themes names
[ https://issues.apache.org/jira/browse/OFBIZ-9863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300201#comment-17300201 ] ASF subversion and git services commented on OFBIZ-9863: Commit e0e1df5eacadaacde9aa39b6d3e0d77e289a9568 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=e0e1df5 ] Fixed: Use Labels in themes names (OFBIZ-9863) Fixes wrong C/P done with r1865370 > Use Labels in themes names > -- > > Key: OFBIZ-9863 > URL: https://issues.apache.org/jira/browse/OFBIZ-9863 > Project: OFBiz > Issue Type: Improvement >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: 18.12.01, 17.12.01 > > > In RainbowStoneThemeData.xml, less sure in Theme.xml (is that data?) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-9863) Use Labels in themes names
[ https://issues.apache.org/jira/browse/OFBIZ-9863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300199#comment-17300199 ] ASF subversion and git services commented on OFBIZ-9863: Commit c32abb81d26ee46724b37dc7a19868345415d070 in ofbiz-framework's branch refs/heads/release17.12 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=c32abb8 ] Fixed: Use Labels in themes names (OFBIZ-9863) Fixes wrong C/P done with r1865370 > Use Labels in themes names > -- > > Key: OFBIZ-9863 > URL: https://issues.apache.org/jira/browse/OFBIZ-9863 > Project: OFBiz > Issue Type: Improvement >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: 18.12.01, 17.12.01 > > > In RainbowStoneThemeData.xml, less sure in Theme.xml (is that data?) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-9863) Use Labels in themes names
[ https://issues.apache.org/jira/browse/OFBIZ-9863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300200#comment-17300200 ] ASF subversion and git services commented on OFBIZ-9863: Commit 742bc4650f3cc206dd70c5e0d1f38d4b4c590d97 in ofbiz-framework's branch refs/heads/release18.12 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=742bc46 ] Fixed: Use Labels in themes names (OFBIZ-9863) Fixes wrong C/P done with r1865370 > Use Labels in themes names > -- > > Key: OFBIZ-9863 > URL: https://issues.apache.org/jira/browse/OFBIZ-9863 > Project: OFBiz > Issue Type: Improvement >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: 18.12.01, 17.12.01 > > > In RainbowStoneThemeData.xml, less sure in Theme.xml (is that data?) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-12193) Cant search ViewEntity InventoryItemDetailForSum
[ https://issues.apache.org/jira/browse/OFBIZ-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300195#comment-17300195 ] Jacques Le Roux edited comment on OFBIZ-12193 at 3/12/21, 10:16 AM: Hi Sebastian, I tried both to apply the patch and to cherry pick commit fabbba3 to R17 to no avail. was (Author: jacques.le.roux): Hi Sebastian, I tried both to apply the patch and to cherry pick commit fabbba3 to no avail. > Cant search ViewEntity InventoryItemDetailForSum > > > Key: OFBIZ-12193 > URL: https://issues.apache.org/jira/browse/OFBIZ-12193 > Project: OFBiz > Issue Type: Bug >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Sebastian Berg >Assignee: Sebastian Berg >Priority: Major > > Go to Entity Engine - > search entity InventoryItemDetailForSum (view entity) > -> search for entries -> an error message is shown. > A SQL exception occurred running the service executeFind -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12193) Cant search ViewEntity InventoryItemDetailForSum
[ https://issues.apache.org/jira/browse/OFBIZ-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300195#comment-17300195 ] Jacques Le Roux commented on OFBIZ-12193: - Hi Sebastian, I tried both to apply the patch and to cherry pick commit fabbba3 to no avail. > Cant search ViewEntity InventoryItemDetailForSum > > > Key: OFBIZ-12193 > URL: https://issues.apache.org/jira/browse/OFBIZ-12193 > Project: OFBiz > Issue Type: Bug >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Sebastian Berg >Assignee: Sebastian Berg >Priority: Major > > Go to Entity Engine - > search entity InventoryItemDetailForSum (view entity) > -> search for entries -> an error message is shown. > A SQL exception occurred running the service executeFind -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12193) Cant search ViewEntity InventoryItemDetailForSum
[ https://issues.apache.org/jira/browse/OFBIZ-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300190#comment-17300190 ] ASF subversion and git services commented on OFBIZ-12193: - Commit fabbba342c992e5bad48be269e75ca9ef86e9d3d in ofbiz-framework's branch refs/heads/release18.12 from SebastianEcomify [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=fabbba3 ] Fixed: Addressed log issues caused in FindGeneric.groovy (OFBIZ-12193) (#285) The backportet Version of searchForm in FindGeneric.groovy was to advanced for the 18.12 Version. The form was changed back to its previous version and the changes causing the view Error in ViewEntities have been worked into it > Cant search ViewEntity InventoryItemDetailForSum > > > Key: OFBIZ-12193 > URL: https://issues.apache.org/jira/browse/OFBIZ-12193 > Project: OFBiz > Issue Type: Bug >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Sebastian Berg >Assignee: Sebastian Berg >Priority: Major > > Go to Entity Engine - > search entity InventoryItemDetailForSum (view entity) > -> search for entries -> an error message is shown. > A SQL exception occurred running the service executeFind -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [ofbiz-framework] JacquesLeRoux merged pull request #285: OFBIZ-12193 Fixed: Addressed log issues caused in FindGeneric.groovy
JacquesLeRoux merged pull request #285: URL: https://github.com/apache/ofbiz-framework/pull/285 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (OFBIZ-12195) webtools/control/threadList no longer works on trunk (only)
[ https://issues.apache.org/jira/browse/OFBIZ-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-12195. --- Fix Version/s: (was: Upcoming Branch) 17.12.06 18.12.01 Resolution: Fixed > webtools/control/threadList no longer works on trunk (only) > --- > > Key: OFBIZ-12195 > URL: https://issues.apache.org/jira/browse/OFBIZ-12195 > Project: OFBiz > Issue Type: Sub-task > Components: framework/webtools >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.01, 17.12.06 > > > This can be currently tested at > https://demo-trunk.ofbiz.apache.org/webtools/control/threadList > R18 and R17 are OK -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12195) webtools/control/threadList no longer works on trunk (only)
[ https://issues.apache.org/jira/browse/OFBIZ-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300126#comment-17300126 ] ASF subversion and git services commented on OFBIZ-12195: - Commit 75e02470485f600e17113dae60b92fe208c0c203 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=75e0247 ] Fixed: webtools/control/threadList no longer works on trunk (only) (OFBIZ-12195) It works if we downgrade Freemarker to 2.3.28 as in R18 and even using 2.3.29, not 2.3.30. Handles things at the Groovy level, ie put in context, rather than creating in Freemarker template. It's backported, even if it's not a pb but in trunk, because it's a (low) security issue. > webtools/control/threadList no longer works on trunk (only) > --- > > Key: OFBIZ-12195 > URL: https://issues.apache.org/jira/browse/OFBIZ-12195 > Project: OFBiz > Issue Type: Sub-task > Components: framework/webtools >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > This can be currently tested at > https://demo-trunk.ofbiz.apache.org/webtools/control/threadList > R18 and R17 are OK -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12195) webtools/control/threadList no longer works on trunk (only)
[ https://issues.apache.org/jira/browse/OFBIZ-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300124#comment-17300124 ] ASF subversion and git services commented on OFBIZ-12195: - Commit 9dd2a255e95c10588004e4fdfb794ab23d173103 in ofbiz-framework's branch refs/heads/release17.12 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=9dd2a25 ] Fixed: webtools/control/threadList no longer works on trunk (only) (OFBIZ-12195) It works if we downgrade Freemarker to 2.3.28 as in R18 and even using 2.3.29, not 2.3.30. Handles things at the Groovy level, ie put in context, rather than creating in Freemarker template. It's backported, even if it's not a pb but in trunk, because it's a (low) security issue. > webtools/control/threadList no longer works on trunk (only) > --- > > Key: OFBIZ-12195 > URL: https://issues.apache.org/jira/browse/OFBIZ-12195 > Project: OFBiz > Issue Type: Sub-task > Components: framework/webtools >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > This can be currently tested at > https://demo-trunk.ofbiz.apache.org/webtools/control/threadList > R18 and R17 are OK -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12195) webtools/control/threadList no longer works on trunk (only)
[ https://issues.apache.org/jira/browse/OFBIZ-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300125#comment-17300125 ] ASF subversion and git services commented on OFBIZ-12195: - Commit 82c225824785819e5e66b92f6f00d9306e1f620b in ofbiz-framework's branch refs/heads/release18.12 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=82c2258 ] Fixed: webtools/control/threadList no longer works on trunk (only) (OFBIZ-12195) It works if we downgrade Freemarker to 2.3.28 as in R18 and even using 2.3.29, not 2.3.30. Handles things at the Groovy level, ie put in context, rather than creating in Freemarker template. It's backported, even if it's not a pb but in trunk, because it's a (low) security issue. > webtools/control/threadList no longer works on trunk (only) > --- > > Key: OFBIZ-12195 > URL: https://issues.apache.org/jira/browse/OFBIZ-12195 > Project: OFBiz > Issue Type: Sub-task > Components: framework/webtools >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > This can be currently tested at > https://demo-trunk.ofbiz.apache.org/webtools/control/threadList > R18 and R17 are OK -- This message was sent by Atlassian Jira (v8.3.4#803005)
