[jira] [Commented] (OFBIZ-9873) Create a PoC for a documentation system for OFBiz based on Asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467918#comment-16467918 ] Jacques Le Roux commented on OFBIZ-9873: Thanks Sharan, Yes indeed, I can see it in the user doc PDF, but nothing for EntitySync in developer doc. BTW I just saw that this doc is mostly empty. I'll check that... > Create a PoC for a documentation system for OFBiz based on Asciidoc > --- > > Key: OFBIZ-9873 > URL: https://issues.apache.org/jira/browse/OFBIZ-9873 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-9873-rouge-coderay.patch, OFBIZ-9873.patch, > OFBIZ-9873.patch > > > In reference to the [discussion > thread|https://lists.apache.org/thread.html/8cc03b7b8733512244129ddae9e0cc1fb2a28e3e250aba1c8cf678f8@%3Cdev.ofbiz.apache.org%3E] > this is an attempt to create a PoC for OFBiz documentation system based on > Asciidoc. The main assumptions for the design of this system are: > - The documentation language to use is Asciidoc > - The documentation tool is Asciidoctor > - Publishing happens through Gradle using the asciidoctor gradle plugin (not > the OFBiz framework or anything else). > - The only place where we write documentation is inside the code base > - Every component contains its own documentation > - General documentation goes to either a standalone directory or a generic > component like common or base > - As much as possible, documentation files are small and focused on one > topic. And then other longer documents are constructed from these snippets of > documentation. > - We publish to all formats including PDF for users, or HTML for embedded > help and wiki pages. So OFBiz does not parse docbook for its help system, > instead it just renders generated HTML. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9873) Create a PoC for a documentation system for OFBiz based on Asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467483#comment-16467483 ] Sharan Foga commented on OFBIZ-9873: Hi [~jacques.le.roux] I use the generateOfbizDocumentation to test any changes I do for the human resources documentation and the pdf and html for everything is coming out fine for me. > Create a PoC for a documentation system for OFBiz based on Asciidoc > --- > > Key: OFBIZ-9873 > URL: https://issues.apache.org/jira/browse/OFBIZ-9873 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-9873-rouge-coderay.patch, OFBIZ-9873.patch, > OFBIZ-9873.patch > > > In reference to the [discussion > thread|https://lists.apache.org/thread.html/8cc03b7b8733512244129ddae9e0cc1fb2a28e3e250aba1c8cf678f8@%3Cdev.ofbiz.apache.org%3E] > this is an attempt to create a PoC for OFBiz documentation system based on > Asciidoc. The main assumptions for the design of this system are: > - The documentation language to use is Asciidoc > - The documentation tool is Asciidoctor > - Publishing happens through Gradle using the asciidoctor gradle plugin (not > the OFBiz framework or anything else). > - The only place where we write documentation is inside the code base > - Every component contains its own documentation > - General documentation goes to either a standalone directory or a generic > component like common or base > - As much as possible, documentation files are small and focused on one > topic. And then other longer documents are constructed from these snippets of > documentation. > - We publish to all formats including PDF for users, or HTML for embedded > help and wiki pages. So OFBiz does not parse docbook for its help system, > instead it just renders generated HTML. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10338) Confusing entity names
[ https://issues.apache.org/jira/browse/OFBIZ-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467437#comment-16467437 ] Suraj Khurana commented on OFBIZ-10338: --- As per discussion in mailing list, there is no conclusion derived on this ticket yet. > Confusing entity names > -- > > Key: OFBIZ-10338 > URL: https://issues.apache.org/jira/browse/OFBIZ-10338 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > > There are some entities which could be renamed as per their usage. > * *OrderItemShipGroup*: It shows order ship groups and it doesn't contain > anything at order item level. So, it could be re-named as *OrderShipGroup.* > * *OrderItemShipGroupAssoc:* It do not maintain any association type, it > just contains order item with respect to ship group, so this could be > re-named as *OrderShipGroupItem* to maintain consistency and code readablity. > There is a discussion as well on Dev ML regarding this improvement. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10374) Existing BILLING_LOCATION record of party should expire while creating a new one
[ https://issues.apache.org/jira/browse/OFBIZ-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki closed OFBIZ-10374. - > Existing BILLING_LOCATION record of party should expire while creating a new > one > > > Key: OFBIZ-10374 > URL: https://issues.apache.org/jira/browse/OFBIZ-10374 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk, Release Branch 16.11, Upcoming Branch >Reporter: Suraj Khurana >Assignee: Rishi Solanki >Priority: Minor > Fix For: Release Branch 16.11, Upcoming Branch > > Attachments: OFBIZ-10374.patch > > > In createUpdateBillingAddress service, it is not handled properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10374) Existing BILLING_LOCATION record of party should expire while creating a new one
[ https://issues.apache.org/jira/browse/OFBIZ-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467435#comment-16467435 ] Suraj Khurana commented on OFBIZ-10374: --- Thanks [~rishisolankii], :) > Existing BILLING_LOCATION record of party should expire while creating a new > one > > > Key: OFBIZ-10374 > URL: https://issues.apache.org/jira/browse/OFBIZ-10374 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk, Release Branch 16.11, Upcoming Branch >Reporter: Suraj Khurana >Assignee: Rishi Solanki >Priority: Minor > Fix For: Release Branch 16.11, Upcoming Branch > > Attachments: OFBIZ-10374.patch > > > In createUpdateBillingAddress service, it is not handled properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-10374) Existing BILLING_LOCATION record of party should expire while creating a new one
[ https://issues.apache.org/jira/browse/OFBIZ-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki resolved OFBIZ-10374. --- Resolution: Fixed Fix Version/s: Release Branch 16.11 Upcoming Branch > Existing BILLING_LOCATION record of party should expire while creating a new > one > > > Key: OFBIZ-10374 > URL: https://issues.apache.org/jira/browse/OFBIZ-10374 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk, Release Branch 16.11, Upcoming Branch >Reporter: Suraj Khurana >Assignee: Rishi Solanki >Priority: Minor > Fix For: Upcoming Branch, Release Branch 16.11 > > Attachments: OFBIZ-10374.patch > > > In createUpdateBillingAddress service, it is not handled properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10374) Existing BILLING_LOCATION record of party should expire while creating a new one
[ https://issues.apache.org/jira/browse/OFBIZ-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467433#comment-16467433 ] Rishi Solanki commented on OFBIZ-10374: --- Thanks [~suraj.khurana] for reporting the issue and work, your patch has been committed in trunk revision 1831183, 17.12 revision 1831185 and REL16.11 revision 1831186. > Existing BILLING_LOCATION record of party should expire while creating a new > one > > > Key: OFBIZ-10374 > URL: https://issues.apache.org/jira/browse/OFBIZ-10374 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk, Release Branch 16.11, Upcoming Branch >Reporter: Suraj Khurana >Assignee: Rishi Solanki >Priority: Minor > Attachments: OFBIZ-10374.patch > > > In createUpdateBillingAddress service, it is not handled properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10374) Existing BILLING_LOCATION record of party should expire while creating a new one
[ https://issues.apache.org/jira/browse/OFBIZ-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki updated OFBIZ-10374: -- Affects Version/s: Upcoming Branch Trunk Release Branch 16.11 Component/s: order > Existing BILLING_LOCATION record of party should expire while creating a new > one > > > Key: OFBIZ-10374 > URL: https://issues.apache.org/jira/browse/OFBIZ-10374 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk, Release Branch 16.11, Upcoming Branch >Reporter: Suraj Khurana >Assignee: Rishi Solanki >Priority: Minor > Attachments: OFBIZ-10374.patch > > > In createUpdateBillingAddress service, it is not handled properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10374) Existing BILLING_LOCATION record of party should expire while creating a new one
[ https://issues.apache.org/jira/browse/OFBIZ-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki reassigned OFBIZ-10374: - Assignee: Rishi Solanki (was: Suraj Khurana) > Existing BILLING_LOCATION record of party should expire while creating a new > one > > > Key: OFBIZ-10374 > URL: https://issues.apache.org/jira/browse/OFBIZ-10374 > Project: OFBiz > Issue Type: Bug >Reporter: Suraj Khurana >Assignee: Rishi Solanki >Priority: Minor > Attachments: OFBIZ-10374.patch > > > In createUpdateBillingAddress service, it is not handled properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-9873) Create a PoC for a documentation system for OFBiz based on Asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467299#comment-16467299 ] Jacques Le Roux edited comment on OFBIZ-9873 at 5/8/18 11:58 AM: - Hi Taher, bq. So can you share what you did exactly as a workaround? It seems from some of the research I've done that the problem really won't go away until the folks at asciidoctor release a new version with new dependencies. Yes, I simply replaced rouge by coderay like the Spring team does for now. I suggest that we replace rouge by coderay until rouge works in Windows, see [^OFBIZ-9873-rouge-coderay.patch] for that bq. generateOfbizDocumentation essentially publishes everything consolidated as one But that does not work for framework/entityext/src/doc/asciidoc/EntitySync-manual.adoc It's not included anywhere in a PDF or HTML at generation. So I need to do my own Gradle task or? I see that humanres.adoc has no way to generate the PDF/HTML too. So what do I miss? Are *.adoc like humanres.adoc and EntitySync-manual.adoc not supposed to generate PDF/HTML? I guess we need to discuss that on dev ML, no? was (Author: jacques.le.roux): Hi Taher, bq. So can you share what you did exactly as a workaround? It seems from some of the research I've done that the problem really won't go away until the folks at asciidoctor release a new version with new dependencies. Yes, I simply replaced rouge by coderay like the Spring team does for now. I suggest that we replace rouge by coderay until rouge works in Windows, see [^OFBIZ-9873-rouge-coderay.patch] for that bq. generateOfbizDocumentation essentially publishes everything consolidated as one But that does not work for framework/entityext/src/doc/asciidoc/EntitySync-manual.adoc It's not included anywhere in a PDF or HTML at generation. So I need to do my own Gradle task or? I see that humanres.adoc has no way to generate the PDF/HTML too. So what do I miss? Are *.ad [^OFBIZ-9873-rouge-coderay.patch] oc like humanres.adoc and EntitySync-manual.adoc not supposed to generate PDF/HTML? I guess we need to discuss that on dev ML, no? > Create a PoC for a documentation system for OFBiz based on Asciidoc > --- > > Key: OFBIZ-9873 > URL: https://issues.apache.org/jira/browse/OFBIZ-9873 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-9873-rouge-coderay.patch, OFBIZ-9873.patch, > OFBIZ-9873.patch > > > In reference to the [discussion > thread|https://lists.apache.org/thread.html/8cc03b7b8733512244129ddae9e0cc1fb2a28e3e250aba1c8cf678f8@%3Cdev.ofbiz.apache.org%3E] > this is an attempt to create a PoC for OFBiz documentation system based on > Asciidoc. The main assumptions for the design of this system are: > - The documentation language to use is Asciidoc > - The documentation tool is Asciidoctor > - Publishing happens through Gradle using the asciidoctor gradle plugin (not > the OFBiz framework or anything else). > - The only place where we write documentation is inside the code base > - Every component contains its own documentation > - General documentation goes to either a standalone directory or a generic > component like common or base > - As much as possible, documentation files are small and focused on one > topic. And then other longer documents are constructed from these snippets of > documentation. > - We publish to all formats including PDF for users, or HTML for embedded > help and wiki pages. So OFBiz does not parse docbook for its help system, > instead it just renders generated HTML. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9873) Create a PoC for a documentation system for OFBiz based on Asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467299#comment-16467299 ] Jacques Le Roux commented on OFBIZ-9873: Hi Taher, bq. So can you share what you did exactly as a workaround? It seems from some of the research I've done that the problem really won't go away until the folks at asciidoctor release a new version with new dependencies. Yes, I simply replaced rouge by coderay like the Spring team does for now. I suggest that we replace rouge by coderay until rouge works in Windows, see [^OFBIZ-9873-rouge-coderay.patch] for that bq. generateOfbizDocumentation essentially publishes everything consolidated as one But that does not work for framework/entityext/src/doc/asciidoc/EntitySync-manual.adoc It's not included anywhere in a PDF or HTML at generation. So I need to do my own Gradle task or? I see that humanres.adoc has no way to generate the PDF/HTML too. So what do I miss? Are *.ad [^OFBIZ-9873-rouge-coderay.patch] oc like humanres.adoc and EntitySync-manual.adoc not supposed to generate PDF/HTML? I guess we need to discuss that on dev ML, no? > Create a PoC for a documentation system for OFBiz based on Asciidoc > --- > > Key: OFBIZ-9873 > URL: https://issues.apache.org/jira/browse/OFBIZ-9873 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-9873-rouge-coderay.patch, OFBIZ-9873.patch, > OFBIZ-9873.patch > > > In reference to the [discussion > thread|https://lists.apache.org/thread.html/8cc03b7b8733512244129ddae9e0cc1fb2a28e3e250aba1c8cf678f8@%3Cdev.ofbiz.apache.org%3E] > this is an attempt to create a PoC for OFBiz documentation system based on > Asciidoc. The main assumptions for the design of this system are: > - The documentation language to use is Asciidoc > - The documentation tool is Asciidoctor > - Publishing happens through Gradle using the asciidoctor gradle plugin (not > the OFBiz framework or anything else). > - The only place where we write documentation is inside the code base > - Every component contains its own documentation > - General documentation goes to either a standalone directory or a generic > component like common or base > - As much as possible, documentation files are small and focused on one > topic. And then other longer documents are constructed from these snippets of > documentation. > - We publish to all formats including PDF for users, or HTML for embedded > help and wiki pages. So OFBiz does not parse docbook for its help system, > instead it just renders generated HTML. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9873) Create a PoC for a documentation system for OFBiz based on Asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-9873: --- Attachment: OFBIZ-9873-rouge-coderay.patch > Create a PoC for a documentation system for OFBiz based on Asciidoc > --- > > Key: OFBIZ-9873 > URL: https://issues.apache.org/jira/browse/OFBIZ-9873 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-9873-rouge-coderay.patch, OFBIZ-9873.patch, > OFBIZ-9873.patch > > > In reference to the [discussion > thread|https://lists.apache.org/thread.html/8cc03b7b8733512244129ddae9e0cc1fb2a28e3e250aba1c8cf678f8@%3Cdev.ofbiz.apache.org%3E] > this is an attempt to create a PoC for OFBiz documentation system based on > Asciidoc. The main assumptions for the design of this system are: > - The documentation language to use is Asciidoc > - The documentation tool is Asciidoctor > - Publishing happens through Gradle using the asciidoctor gradle plugin (not > the OFBiz framework or anything else). > - The only place where we write documentation is inside the code base > - Every component contains its own documentation > - General documentation goes to either a standalone directory or a generic > component like common or base > - As much as possible, documentation files are small and focused on one > topic. And then other longer documents are constructed from these snippets of > documentation. > - We publish to all formats including PDF for users, or HTML for embedded > help and wiki pages. So OFBiz does not parse docbook for its help system, > instead it just renders generated HTML. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9873) Create a PoC for a documentation system for OFBiz based on Asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467196#comment-16467196 ] Taher Alkhateeb commented on OFBIZ-9873: Hello Jacques, Thank you for reporting this, it's always good to find these problems across different operating systems. It keeps us careful and on our toes. So can you share what you did exactly as a workaround? It seems from some of the research I've done that the problem really won't go away until the folks at asciidoctor release a new version with new dependencies. As with respect to your question of how to generate a certain document. The answer is, out-of-the-box, you don't. I've designed the system with two commands: generateOfbizDocumentation essentially publishes everything consolidated as one, so you need to "include" whatever you want into the final manual. The other task "generatePluginDocumentation" does the same thing but only for a single component. You can read the implementation in build.gradle to understand the specifics. > Create a PoC for a documentation system for OFBiz based on Asciidoc > --- > > Key: OFBIZ-9873 > URL: https://issues.apache.org/jira/browse/OFBIZ-9873 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-9873.patch, OFBIZ-9873.patch > > > In reference to the [discussion > thread|https://lists.apache.org/thread.html/8cc03b7b8733512244129ddae9e0cc1fb2a28e3e250aba1c8cf678f8@%3Cdev.ofbiz.apache.org%3E] > this is an attempt to create a PoC for OFBiz documentation system based on > Asciidoc. The main assumptions for the design of this system are: > - The documentation language to use is Asciidoc > - The documentation tool is Asciidoctor > - Publishing happens through Gradle using the asciidoctor gradle plugin (not > the OFBiz framework or anything else). > - The only place where we write documentation is inside the code base > - Every component contains its own documentation > - General documentation goes to either a standalone directory or a generic > component like common or base > - As much as possible, documentation files are small and focused on one > topic. And then other longer documents are constructed from these snippets of > documentation. > - We publish to all formats including PDF for users, or HTML for embedded > help and wiki pages. So OFBiz does not parse docbook for its help system, > instead it just renders generated HTML. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10391) Make accounting entry configurable
[ https://issues.apache.org/jira/browse/OFBIZ-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal reassigned OFBIZ-10391: Assignee: (was: Aman Agrawal) > Make accounting entry configurable > -- > > Key: OFBIZ-10391 > URL: https://issues.apache.org/jira/browse/OFBIZ-10391 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Aman Agrawal >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10391.patch > > > In current flow, if we want to disable the accounting then we need to disable > the set of seca's. We don't have any configurable setting to disable > accounting. > We can manage this by adding a new field 'enableAccounting' in the > 'PartyAcctgPreference' entity. Accounting transaction entries will be > entertained accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10391) Make accounting entry configurable
[ https://issues.apache.org/jira/browse/OFBIZ-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467145#comment-16467145 ] Aman Agrawal commented on OFBIZ-10391: -- Hello, In this, I have added one field 'enableAccounting' in the PartyAcctgPreference entity. By this field added a check whether accounting is enable or not in the services used to create accounting transaction entries. I have uploaded the patch for the same. > Make accounting entry configurable > -- > > Key: OFBIZ-10391 > URL: https://issues.apache.org/jira/browse/OFBIZ-10391 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10391.patch > > > In current flow, if we want to disable the accounting then we need to disable > the set of seca's. We don't have any configurable setting to disable > accounting. > We can manage this by adding a new field 'enableAccounting' in the > 'PartyAcctgPreference' entity. Accounting transaction entries will be > entertained accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10391) Make accounting entry configurable
[ https://issues.apache.org/jira/browse/OFBIZ-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-10391: - Attachment: OFBIZ-10391.patch > Make accounting entry configurable > -- > > Key: OFBIZ-10391 > URL: https://issues.apache.org/jira/browse/OFBIZ-10391 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10391.patch > > > In current flow, if we want to disable the accounting then we need to disable > the set of seca's. We don't have any configurable setting to disable > accounting. > We can manage this by adding a new field 'enableAccounting' in the > 'PartyAcctgPreference' entity. Accounting transaction entries will be > entertained accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9873) Create a PoC for a documentation system for OFBiz based on Asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467112#comment-16467112 ] Jacques Le Roux commented on OFBIZ-9873: I replaced rouge by coderay, it works here. I though still don't know how to generate a PDF for EntitySync-manual.adoc. > Create a PoC for a documentation system for OFBiz based on Asciidoc > --- > > Key: OFBIZ-9873 > URL: https://issues.apache.org/jira/browse/OFBIZ-9873 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-9873.patch, OFBIZ-9873.patch > > > In reference to the [discussion > thread|https://lists.apache.org/thread.html/8cc03b7b8733512244129ddae9e0cc1fb2a28e3e250aba1c8cf678f8@%3Cdev.ofbiz.apache.org%3E] > this is an attempt to create a PoC for OFBiz documentation system based on > Asciidoc. The main assumptions for the design of this system are: > - The documentation language to use is Asciidoc > - The documentation tool is Asciidoctor > - Publishing happens through Gradle using the asciidoctor gradle plugin (not > the OFBiz framework or anything else). > - The only place where we write documentation is inside the code base > - Every component contains its own documentation > - General documentation goes to either a standalone directory or a generic > component like common or base > - As much as possible, documentation files are small and focused on one > topic. And then other longer documents are constructed from these snippets of > documentation. > - We publish to all formats including PDF for users, or HTML for embedded > help and wiki pages. So OFBiz does not parse docbook for its help system, > instead it just renders generated HTML. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10214) Update build.gradle to the latest dependencies
[ https://issues.apache.org/jira/browse/OFBIZ-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467102#comment-16467102 ] Jacques Le Roux edited comment on OFBIZ-10214 at 5/8/18 8:52 AM: - I think freemarker 2.3.28 is OK, right? Also certainly at least - javax.servlet:javax.servlet-api [4.0.0 -> 4.0.1] - org.jruby:jruby-complete [9.1.13.0 -> 9.1.16.0] - org.jsoup:jsoup [1.11.2 -> 1.11.3] - com.googlecode.libphonenumber:libphonenumber [8.8.7 -> 8.9.4] - org.apache.logging.log4j:log4j-1.2-api [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-api [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-core [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-jul [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-slf4j-impl [2.10.0 -> 2.11.0] Maybe - org.apache.lucene:lucene-analyzers-common [7.2.1 -> 7.3.0] - org.apache.lucene:lucene-core [7.2.1 -> 7.3.0] - org.apache.lucene:lucene-queryparser [7.2.1 -> 7.3.0] - org.mockito:mockito-core [2.13.0 -> 2.18.3] - org.apache.poi:poi-excelant [3.14 -> 3.17] - org.apache.poi:poi-ooxml [3.14 -> 3.17] - org.apache.poi:poi-ooxml-schemas [3.14 -> 3.17] - org.apache.poi:poi-scratchpad [3.14 -> 3.17] - org.apache.solr:solr-core [7.2.1 -> 7.3.0] - org.springframework:spring-test [5.0.2.RELEASE -> 5.0.5.RELEASE] - org.apache.tika:tika-core [1.16 -> 1.17] - org.apache.tika:tika-parsers [1.16 -> 1.17] And though unsure why not - org.apache.ant:ant-junit [1.10.1 -> 1.10.3] - org.apache.ant:ant-junit [1.9.7 -> 1.10.3] - org.jasig.cas:cas-server-core [3.3.5 -> 4.2.7] - com.google.zxing:core [3.3.1 -> 3.3.2] So it seems it's almost all For tomcat-embed-websocket Deepak did it already, I simply forgot to update plugins before running dependencyUpdates was (Author: jacques.le.roux): I think freemarker 2.3.28 is OK, right? Also certainly at least - javax.servlet:javax.servlet-api [4.0.0 -> 4.0.1] - org.jruby:jruby-complete [9.1.13.0 -> 9.1.16.0] - org.jsoup:jsoup [1.11.2 -> 1.11.3] - com.googlecode.libphonenumber:libphonenumber [8.8.7 -> 8.9.4] - org.apache.logging.log4j:log4j-1.2-api [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-api [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-core [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-jul [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-slf4j-impl [2.10.0 -> 2.11.0] Maybe - org.apache.lucene:lucene-analyzers-common [7.2.1 -> 7.3.0] - org.apache.lucene:lucene-core [7.2.1 -> 7.3.0] - org.apache.lucene:lucene-queryparser [7.2.1 -> 7.3.0] - org.mockito:mockito-core [2.13.0 -> 2.18.3] - org.apache.poi:poi-excelant [3.14 -> 3.17] - org.apache.poi:poi-ooxml [3.14 -> 3.17] - org.apache.poi:poi-ooxml-schemas [3.14 -> 3.17] - org.apache.poi:poi-scratchpad [3.14 -> 3.17] - org.apache.solr:solr-core [7.2.1 -> 7.3.0] - org.springframework:spring-test [5.0.2.RELEASE -> 5.0.5.RELEASE] - org.apache.tika:tika-core [1.16 -> 1.17] - org.apache.tika:tika-parsers [1.16 -> 1.17] For tomcat-embed-websocket Deepak did it already, I simply forgot to update plugins before running dependencyUpdates > Update build.gradle to the latest dependencies > -- > > Key: OFBIZ-10214 > URL: https://issues.apache.org/jira/browse/OFBIZ-10214 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > I'll for now wait because of OFBIZ-10036 which concerns upgrading to Tomcat 9 > and should be the most important part of the work -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10214) Update build.gradle to the latest dependencies
[ https://issues.apache.org/jira/browse/OFBIZ-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467102#comment-16467102 ] Jacques Le Roux commented on OFBIZ-10214: - I think freemarker 2.3.28 is OK, right? Also certainly at least - javax.servlet:javax.servlet-api [4.0.0 -> 4.0.1] - org.jruby:jruby-complete [9.1.13.0 -> 9.1.16.0] - org.jsoup:jsoup [1.11.2 -> 1.11.3] - com.googlecode.libphonenumber:libphonenumber [8.8.7 -> 8.9.4] - org.apache.logging.log4j:log4j-1.2-api [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-api [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-core [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-jul [2.10.0 -> 2.11.0] - org.apache.logging.log4j:log4j-slf4j-impl [2.10.0 -> 2.11.0] Maybe - org.apache.lucene:lucene-analyzers-common [7.2.1 -> 7.3.0] - org.apache.lucene:lucene-core [7.2.1 -> 7.3.0] - org.apache.lucene:lucene-queryparser [7.2.1 -> 7.3.0] - org.mockito:mockito-core [2.13.0 -> 2.18.3] - org.apache.poi:poi-excelant [3.14 -> 3.17] - org.apache.poi:poi-ooxml [3.14 -> 3.17] - org.apache.poi:poi-ooxml-schemas [3.14 -> 3.17] - org.apache.poi:poi-scratchpad [3.14 -> 3.17] - org.apache.solr:solr-core [7.2.1 -> 7.3.0] - org.springframework:spring-test [5.0.2.RELEASE -> 5.0.5.RELEASE] - org.apache.tika:tika-core [1.16 -> 1.17] - org.apache.tika:tika-parsers [1.16 -> 1.17] For tomcat-embed-websocket Deepak did it already, I simply forgot to update plugins before running dependencyUpdates > Update build.gradle to the latest dependencies > -- > > Key: OFBIZ-10214 > URL: https://issues.apache.org/jira/browse/OFBIZ-10214 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > I'll for now wait because of OFBIZ-10036 which concerns upgrading to Tomcat 9 > and should be the most important part of the work -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10213) Update build.gradle to the latest dependencies
[
https://issues.apache.org/jira/browse/OFBIZ-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-10213:
Description:
We want to check from time to time if we need to update the dependencies.
It's easyly done with the [gradle-versions-plugin
|https://github.com/ben-manes/gradle-versions-plugin] which analyzes the
dependencies and checks if there are newer versions available.
Using this patch
{code}
Index: build.gradle
===
--- build.gradle(révision 1831078)
+++ build.gradle(copie de travail)
@@ -33,6 +33,7 @@
classpath 'org.asciidoctor:asciidoctorj-pdf:1.5.0-alpha.16'
// asciidoctorj-pdf bug workaround - override jruby. See OFBIZ-9873
classpath 'org.jruby:jruby-complete:9.1.13.0'
+classpath 'com.github.ben-manes:gradle-versions-plugin:0.17.0'
}
}
apply plugin: 'java'
@@ -40,6 +41,7 @@
apply plugin: 'maven-publish'
apply plugin: "at.bxm.svntools"
apply plugin: 'org.asciidoctor.convert'
+apply plugin: 'com.github.ben-manes.versions'
apply from: 'common.gradle'
{code}
And running the check with
{code:java}
./gradlew dependencyUpdates -Drevision=release
{code}
We get a list of dependencies to update. This is an umbrella task for action
tasks.
was:
We want to check from time to time if we need to update the dependencies.
It's easyly done with the [gradle-versions-plugin
|https://github.com/ben-manes/gradle-versions-plugin] which analyzes the
dependencies and checks if there are newer versions available.
Using this patch
{code}
Index: build.gradle
===
--- build.gradle(révision 1823644)
+++ build.gradle(copie de travail)
@@ -28,6 +28,7 @@
}
dependencies {
classpath "at.bxm.gradleplugins:gradle-svntools-plugin:latest.release"
+ classpath 'com.github.ben-manes:gradle-versions-plugin:0.17.0'
}
}
apply plugin: 'java'
@@ -34,6 +35,7 @@
apply plugin: 'eclipse'
apply plugin: 'maven-publish'
apply plugin: "at.bxm.svntools"
+apply plugin: 'com.github.ben-manes.versions'
apply from: 'common.gradle'
{code}
And running the check with
{code:java}
./gradlew dependencyUpdates -Drevision=release
{code}
We get a list of dependencies to update. This is an umbrella task for action
tasks.
> Update build.gradle to the latest dependencies
> --
>
> Key: OFBIZ-10213
> URL: https://issues.apache.org/jira/browse/OFBIZ-10213
> Project: OFBiz
> Issue Type: Task
> Components: Gradle
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Trivial
>
> We want to check from time to time if we need to update the dependencies.
> It's easyly done with the [gradle-versions-plugin
> |https://github.com/ben-manes/gradle-versions-plugin] which analyzes the
> dependencies and checks if there are newer versions available.
> Using this patch
> {code}
> Index: build.gradle
> ===
> --- build.gradle(révision 1831078)
> +++ build.gradle(copie de travail)
> @@ -33,6 +33,7 @@
> classpath 'org.asciidoctor:asciidoctorj-pdf:1.5.0-alpha.16'
> // asciidoctorj-pdf bug workaround - override jruby. See OFBIZ-9873
> classpath 'org.jruby:jruby-complete:9.1.13.0'
> +classpath 'com.github.ben-manes:gradle-versions-plugin:0.17.0'
> }
> }
> apply plugin: 'java'
> @@ -40,6 +41,7 @@
> apply plugin: 'maven-publish'
> apply plugin: "at.bxm.svntools"
> apply plugin: 'org.asciidoctor.convert'
> +apply plugin: 'com.github.ben-manes.versions'
>
> apply from: 'common.gradle'
> {code}
> And running the check with
> {code:java}
> ./gradlew dependencyUpdates -Drevision=release
> {code}
> We get a list of dependencies to update. This is an umbrella task for action
> tasks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10214) Update build.gradle to the latest dependencies
[
https://issues.apache.org/jira/browse/OFBIZ-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467085#comment-16467085
]
Jacques Le Roux commented on OFBIZ-10214:
-
Before I thnink we should have a look at
{code}
C:\projectsASF\ofbiz>gradlew dependencyUpdates -Drevision=release
:dependencyUpdates
Download
https://jcenter.bintray.com/com/googlecode/libphonenumber/libphonenumber/8.9.4/libphonenumber-8.9.4.pom
Download
https://jcenter.bintray.com/com/googlecode/libphonenumber/libphonenumber-parent/8.9.4/libphonenumber-parent-8.9.4.pom
Download https://jcenter.bintray.com/com/ibm/icu/icu4j/61.1/icu4j-61.1.pom
Download
https://jcenter.bintray.com/com/sun/mail/javax.mail/1.6.1/javax.mail-1.6.1.pom
Download https://jcenter.bintray.com/com/sun/mail/all/1.6.1/all-1.6.1.pom
Download
https://jcenter.bintray.com/javax/servlet/javax.servlet-api/4.0.1/javax.servlet-api-4.0.1.pom
Download
https://jcenter.bintray.com/org/apache/ant/ant-junit/1.10.3/ant-junit-1.10.3.pom
Download
https://jcenter.bintray.com/org/apache/ant/ant-parent/1.10.3/ant-parent-1.10.3.pom
Download
https://jcenter.bintray.com/org/apache/logging/log4j/log4j-api/2.11.0/log4j-api-2.11.0.pom
Download
https://jcenter.bintray.com/org/apache/logging/log4j/log4j/2.11.0/log4j-2.11.0.pom
Download
https://jcenter.bintray.com/org/codehaus/groovy/groovy-all/3.0.0-alpha-2/groovy-all-3.0.0-alpha-2.pom
Download
https://jcenter.bintray.com/org/springframework/spring-test/5.0.5.RELEASE/spring-test-5.0.5.RELEASE.pom
Download
https://jcenter.bintray.com/io/projectreactor/reactor-bom/Bismuth-SR8/reactor-bom-Bismuth-SR8.pom
Download
https://jcenter.bintray.com/io/netty/netty-bom/4.1.22.Final/netty-bom-4.1.22.Final.pom
Download https://jcenter.bintray.com/org/jsoup/jsoup/1.11.3/jsoup-1.11.3.pom
Download
https://jcenter.bintray.com/org/apache/logging/log4j/log4j-1.2-api/2.11.0/log4j-1.2-api-2.11.0.pom
Download
https://jcenter.bintray.com/org/apache/logging/log4j/log4j-core/2.11.0/log4j-core-2.11.0.pom
Download
https://jcenter.bintray.com/org/apache/logging/log4j/log4j-jul/2.11.0/log4j-jul-2.11.0.pom
Download
https://jcenter.bintray.com/org/apache/logging/log4j/log4j-slf4j-impl/2.11.0/log4j-slf4j-impl-2.11.0.pom
Download
https://jcenter.bintray.com/org/mockito/mockito-core/2.18.3/mockito-core-2.18.3.pom
Download
https://jcenter.bintray.com/org/jruby/jruby-complete/9.1.16.0/jruby-complete-9.1.16.0.pom
Download
https://jcenter.bintray.com/org/jruby/jruby-artifacts/9.1.16.0/jruby-artifacts-9.1.16.0.pom
Download
https://jcenter.bintray.com/org/jruby/jruby-parent/9.1.16.0/jruby-parent-9.1.16.0.pom
Download
https://jcenter.bintray.com/org/apache/tomcat/embed/tomcat-embed-websocket/9.0.7/tomcat-embed-websocket-9.0.7.pom
Download
https://jcenter.bintray.com/org/apache/lucene/lucene-core/7.3.0/lucene-core-7.3.0.pom
Download
https://jcenter.bintray.com/org/apache/lucene/lucene-parent/7.3.0/lucene-parent-7.3.0.pom
Download
https://jcenter.bintray.com/org/apache/lucene/lucene-solr-grandparent/7.3.0/lucene-solr-grandparent-7.3.0.pom
Download
https://jcenter.bintray.com/org/apache/lucene/lucene-queryparser/7.3.0/lucene-queryparser-7.3.0.pom
Download
https://jcenter.bintray.com/org/apache/lucene/lucene-analyzers-common/7.3.0/lucene-analyzers-common-7.3.0.pom
Download
https://jcenter.bintray.com/org/apache/solr/solr-core/7.3.0/solr-core-7.3.0.pom
Download
https://jcenter.bintray.com/org/apache/solr/solr-parent/7.3.0/solr-parent-7.3.0.pom
> Building 0% > :dependencyUpdates
: Project Dependency Updates (report to plain text file)
The following dependencies are using the latest release version:
- org.asciidoctor:asciidoctor-gradle-plugin:1.5.7
- org.asciidoctor:asciidoctorj-pdf:1.5.0-alpha.16
- org.apache.axis2:axis2-kernel:1.7.7
- org.apache.axis2:axis2-transport-http:1.7.7
- org.apache.axis2:axis2-transport-local:1.7.7
- net.sf.barcode4j:barcode4j:2.1
- net.sf.barcode4j:barcode4j-fop-ext:2.1
- org.codeartisans.thirdparties.swing:batik-all:1.8pre-r1084380
- commons-cli:commons-cli:1.4
- org.apache.commons:commons-collections4:4.1
- org.apache.commons:commons-csv:1.5
- org.apache.commons:commons-dbcp2:2.2.0
- commons-net:commons-net:3.6
- commons-validator:commons-validator:1.6
- com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:1.4.2
- org.apache.derby:derby:10.14.1.0
- org.owasp.esapi:esapi:2.1.0.1
- com.googlecode.ez-vcard:ez-vcard:0.9.10
- org.apache.xmlgraphics:fop:2.2
- org.apache.geronimo.specs:geronimo-jms_1.1_spec:1.1.1
- org.apache.geronimo.components:geronimo-transaction:3.1.4
- at.bxm.gradleplugins:gradle-svntools-plugin:2.2.1
- com.github.ben-manes:gradle-versions-plugin:0.17.0
- com.google.guava:guava:20.0
- org.hamcrest:hamcrest-all:1.3
- net.fortuna.ical4j:ical4j:1.0-rc3-atlassian-11
-
[jira] [Commented] (OFBIZ-9873) Create a PoC for a documentation system for OFBiz based on Asciidoc
[
https://issues.apache.org/jira/browse/OFBIZ-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467076#comment-16467076
]
Jacques Le Roux commented on OFBIZ-9873:
BTW here is the complete stacktrace to show that it's different from the
problem I got earlier (resolved with {{classpath
'org.jruby:jruby-complete:9.1.13.0'}}
{code}
C:\projectsASF\ofbiz>gradlew --stacktrace generateOfbizDocumentation
Parallel execution is an incubating feature.
:deleteOfbizDocumentation
:generateOfbizDocumentation
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:71: warning: already
initialized constant Text
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:71: warning: already
initialized constant Error
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:71: warning: already
initialized constant Other
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:71: warning: already
initialized constant Keyword
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:71: warning: already
initialized constant Name
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:71: warning: already
initialized constant Literal
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:71: warning: already
initialized constant Operator
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:71: warning: already
initialized constant Punctuation
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:71: warning: already
initialized constant Comment
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:71: warning: already
initialized constant Generic
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:178: warning: already
initialized constant Num
uri:classloader:/gems/rouge-2.0.7/lib/rouge/token.rb:179: warning: already
initialized constant Str
uri:classloader:/gems/rouge-2.0.7/lib/rouge/guessers/modeline.rb:5: warning:
already initialized constant EMACS_MODELINE
uri:classloader:/gems/rouge-2.0.7/lib/rouge/guessers/modeline.rb:10: warning:
already initialized constant VIM_MODELINE_1
uri:classloader:/gems/rouge-2.0.7/lib/rouge/guessers/modeline.rb:15: warning:
already initialized constant VIM_MODELINE_2
uri:classloader:/gems/rouge-2.0.7/lib/rouge/guessers/modeline.rb:17: warning:
already initialized constant MODELINES
uri:classloader:/gems/rouge-2.0.7/lib/rouge/regex_lexer.rb:279: warning:
already initialized constant MAX_NULL_SCANS
uri:classloader:/gems/rouge-2.0.7/lib/rouge/lexers/bsl.rb:11: warning: already
initialized constant KEYWORDS
uri:classloader:/gems/rouge-2.0.7/lib/rouge/lexers/bsl.rb:29: warning: already
initialized constant BUILTINS
(RuntimeError) asciidoctor: FAILED: required gem 'rouge' is not installed.
Processing aborted.
:generateOfbizDocumentation FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':generateOfbizDocumentation'.
> Error running Asciidoctor
* Try:
Run with --info or --debug option to get more log output.
* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task
':generateOfbizDocumentation'.
at
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:84)
at
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:55)
at
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:61)
at
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)
at
org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:45)
at
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:51)
at
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at
org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:233)
at
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:215)
at
org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:74)
at
org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:55)
at
[jira] [Commented] (OFBIZ-10214) Update build.gradle to the latest dependencies
[ https://issues.apache.org/jira/browse/OFBIZ-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467010#comment-16467010 ] Jacopo Cappellato commented on OFBIZ-10214: --- can we close this ticket? > Update build.gradle to the latest dependencies > -- > > Key: OFBIZ-10214 > URL: https://issues.apache.org/jira/browse/OFBIZ-10214 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > I'll for now wait because of OFBIZ-10036 which concerns upgrading to Tomcat 9 > and should be the most important part of the work -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10036) Update to Tomcat 9.0.x
[
https://issues.apache.org/jira/browse/OFBIZ-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacopo Cappellato closed OFBIZ-10036.
-
> Update to Tomcat 9.0.x
> --
>
> Key: OFBIZ-10036
> URL: https://issues.apache.org/jira/browse/OFBIZ-10036
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Jacopo Cappellato
>Priority: Minor
> Fix For: 17.12.01
>
> Attachments: OFBIZ-10036.patch
>
>
> We should try to update from Tomcat 8.5.24 to 9.0.2 or later.
> A first try during the work on OFBIZ-10026 causes the tests to hang when
> starting the testXmlMacroLibrary tests. There is no error, just no activity
> after more than 30 minutes.
> {noformat}
> 2017-12-02 18:56:49,658 |main |TestRunContainer
> |I| [JUNIT] : service-xml-rpc-local-engine finished.
> 2017-12-02 18:56:49,658 |main |GenericDelegator
> |I| Rolling back 52 entity operations
> 2017-12-02 18:56:49,783 |main |TestRunContainer
> |I| [JUNIT] Results for test suite: servicetests
> 2017-12-02 18:56:49,783 |main |TestRunContainer
> |I| [JUNIT] Pass: true | # Tests: 31 | # Failed: 0 # Errors: 0
> 2017-12-02 18:56:49,789 |main |TestRunContainer
> |I| [JUNIT] : testXmlMacroLibrary starting...
> {noformat}
> This will need further investigation and maybe an in-depth check of the
> documentation, see
> https://tomcat.apache.org/migration-9.html#Migrating_from_8.0.x_or_8.5.x_to_9.0.x
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
