[jira] [Commented] (OFBIZ-9233) Enable a service to run by a specific service engine
[ https://issues.apache.org/jira/browse/OFBIZ-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315569#comment-16315569 ] Shi Jinghai commented on OFBIZ-9233: I'm working on this issue, I'll try to create a new patch to comply with the new pattern Nicolas mentioned. > Enable a service to run by a specific service engine > > > Key: OFBIZ-9233 > URL: https://issues.apache.org/jira/browse/OFBIZ-9233 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Shi Jinghai >Assignee: Shi Jinghai >Priority: Minor > Attachments: OFBIZ-9233-20170301.patch, OFBIZ-9233-20170413.patch, > OFBIZ-9233-MultiServiceEnginesEnv.png > > > Currently, all of the services of OFBiz are run by the 'default' service > engine. > In a project, we have to make a service run by different service engines > rather than the 'default' one, i.e. order services run by 'order' service > engine and 'orderpool', shipment services run by 'shipment' service engine > and 'shipmentpool'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-6858) Solr logging doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315560#comment-16315560 ] Shi Jinghai commented on OFBIZ-6858: Yes, we can wait a little bit but I'm afraid it would be similar to the qr case of barcode4j, one year later, it's still no change. I'm willing to try SOLR-7887 this week. > Solr logging doesn't work > - > > Key: OFBIZ-6858 > URL: https://issues.apache.org/jira/browse/OFBIZ-6858 > Project: OFBiz > Issue Type: Bug > Components: solr >Affects Versions: Trunk, Release Branch 15.12 >Reporter: Pierre Smits >Assignee: Shi Jinghai > Attachments: Image2.png > > > When looking at the logging screen in demo-trunk > (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are > shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level > provide any insights. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9160) upgrade gradle to version 3.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-9160: --- Fix Version/s: (was: Trunk) I don't know if you noticed but we don't put trunk in fixed version, removing it. [It's explained here.|https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Committers+Roles+and+Responsibilities#OFBizCommittersRolesandResponsibilities-ManageJIRA%27sissues] Recentlly though [someone (I guess Jacopo, but nobody spoke about) removed "Upcoming Branch" and created the next coming branch which is now 17.12.01|https://issues.apache.org/jira/plugins/servlet/project-config/OFBIZ/versions] . I agree it's a clearer way to set things. Actually in "Fix version/s" we should only put unreleased versions and also not trunk, which is never released. So it's 17.12.01 for change in trunk and 17.12.01 + 16.11.05 when backported. The same pattern will apply for any unreleased versions in future and we need to update the wiki (remove "Upcoming Branch" referenced there) > upgrade gradle to version 3.2.1 > --- > > Key: OFBIZ-9160 > URL: https://issues.apache.org/jira/browse/OFBIZ-9160 > Project: OFBiz > Issue Type: Improvement >Affects Versions: 17.12.01 >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, upgrade > Fix For: 17.12.01 > > > Upgrading the gradle build system to version 3.2.1 requires also upgrading > the buildbot scripts accordingly. > The proposal thread is referenced > [here|https://lists.apache.org/thread.html/4ba79bbd595f0d31f46b7402134b8392ecc5715098e93b2e5771b83f@%3Cdev.ofbiz.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9160) upgrade gradle to version 3.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315457#comment-16315457 ] Michael Brohl edited comment on OFBIZ-9160 at 1/7/18 8:15 PM: -- Sure, Taher, please close. I will create a new issue for the next update and set a „blocked by“ reference to the mentioned issue. Can you give me a notice if you solved it? No need to hurry, this is not an urgent task. was (Author: mbrohl): Sure, Taher, please close. I will create a new issue for the next update and set a „blocked by“ reference to the mentioned issue. Can you Five me a notice if you solved it? No need to hurry, this is not an urgent task. > upgrade gradle to version 3.2.1 > --- > > Key: OFBIZ-9160 > URL: https://issues.apache.org/jira/browse/OFBIZ-9160 > Project: OFBiz > Issue Type: Improvement >Affects Versions: 17.12.01 >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, upgrade > > Upgrading the gradle build system to version 3.2.1 requires also upgrading > the buildbot scripts accordingly. > The proposal thread is referenced > [here|https://lists.apache.org/thread.html/4ba79bbd595f0d31f46b7402134b8392ecc5715098e93b2e5771b83f@%3Cdev.ofbiz.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9160) upgrade gradle to version 3.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315457#comment-16315457 ] Michael Brohl commented on OFBIZ-9160: -- Sure, Taher, please close. I will create a new issue for the next update and set a „blocked by“ reference to the mentioned issue. Can you Five me a notice if you solved it? No need to hurry, this is not an urgent task. > upgrade gradle to version 3.2.1 > --- > > Key: OFBIZ-9160 > URL: https://issues.apache.org/jira/browse/OFBIZ-9160 > Project: OFBiz > Issue Type: Improvement >Affects Versions: 17.12.01 >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, upgrade > > Upgrading the gradle build system to version 3.2.1 requires also upgrading > the buildbot scripts accordingly. > The proposal thread is referenced > [here|https://lists.apache.org/thread.html/4ba79bbd595f0d31f46b7402134b8392ecc5715098e93b2e5771b83f@%3Cdev.ofbiz.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9160) upgrade gradle to version 3.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315453#comment-16315453 ] Taher Alkhateeb commented on OFBIZ-9160: For some reason I completely forgot to close this ticket. The update has been done already and I can close this ticket if you're okay with it? Now with respect to upgrading gradle to a new version, my recommendation is to wait. There is a real problem I'm facing (still thinking about it) to which I created a new JIRA OFBIZ-9972. Upgrading to a newer gradle version would automatically mean breaking the syntax (at least getting a warning and eventually breaking it) for ofbiz server commands. > upgrade gradle to version 3.2.1 > --- > > Key: OFBIZ-9160 > URL: https://issues.apache.org/jira/browse/OFBIZ-9160 > Project: OFBiz > Issue Type: Improvement >Affects Versions: 17.12.01 >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, upgrade > > Upgrading the gradle build system to version 3.2.1 requires also upgrading > the buildbot scripts accordingly. > The proposal thread is referenced > [here|https://lists.apache.org/thread.html/4ba79bbd595f0d31f46b7402134b8392ecc5715098e93b2e5771b83f@%3Cdev.ofbiz.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-6858) Solr logging doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315450#comment-16315450 ] Jacques Le Roux commented on OFBIZ-6858: So for an OOTB solution it all depends on SOLR-7887 except if we can override not using log4j-1.2-api and log4j-slf4j-impl in lugins/solr/build.gradle (did not find anything about that) > Solr logging doesn't work > - > > Key: OFBIZ-6858 > URL: https://issues.apache.org/jira/browse/OFBIZ-6858 > Project: OFBiz > Issue Type: Bug > Components: solr >Affects Versions: Trunk, Release Branch 15.12 >Reporter: Pierre Smits >Assignee: Shi Jinghai > Attachments: Image2.png > > > When looking at the logging screen in demo-trunk > (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are > shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level > provide any insights. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9800) French translation of OFBiz website
[ https://issues.apache.org/jira/browse/OFBIZ-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-9800: -- Attachment: website-fr.tar.gz update with svn 1820400 > French translation of OFBiz website > --- > > Key: OFBIZ-9800 > URL: https://issues.apache.org/jira/browse/OFBIZ-9800 > Project: OFBiz > Issue Type: Improvement > Components: site >Reporter: Olivier Heintz >Priority: Minor > Attachments: website-fr.tar, website-fr.tar.gz, website-fr.tar.gz > > > To evaluate the workload of translate all the ofbiz website page in french, > and so to maintain the translation when there are some modifications, I have > start to translate them. > There are between 10 and 15 page to translate, and translate one is between 1 > and 2 hours. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315404#comment-16315404 ] Michael Brohl commented on OFBIZ-9147: -- It was closed because the only provided solution during more than a year was disabling the automatic loading of the exampleext component. No other solution was provided and the current state of the codebase has the same impact as the provided patch: the component is not loaded automatically with the framework. So closing was the obvious action and the resolution is correct. Removing the component was a different topic brought up later, after closing. Who can foresee that? If you want the plugin to be removed, which is a valid proposal, you can always file a new issue for it. Be sure that I will not remove a component/plugin from the codebase without a consensus in the community, so you will have to start a discussion about it in the dev list. If there is a majority of voices who want to remove this plugin, I'm happy to do it as with every other issue. > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315402#comment-16315402 ] Pierre Smits commented on OFBIZ-9147: - Anyway, it goes to show that this ticket was closed prematurely and unnecessary noise was created by the one who did that that. With the words of Jacques: 'you're not deciding alone'. > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315399#comment-16315399 ] Michael Brohl edited comment on OFBIZ-9147 at 1/7/18 5:32 PM: -- (edit: this answers Pierre's previous comment). Then the issue should read "Remove the exampleext plugin from the codebase" or "Move examplext functionality to example" or similar. The original intent of the provided patch (don't load exampleext OOTB ) is outdated/already solved and there is no other solution provided. Please discuss the removal in the dev list and we will take action according to the consensus, thank you. was (Author: mbrohl): Then the issue should read "Remove the exampleext plugin from the codebase" or "Move examplext functionality to example" or similar. The original intent of the provided patch (don't load exampleext OOTB ) is outdated/already solved and there is no other solution provided. Please discuss the removal in the dev list and we will take action according to the consensus, thank you. > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315399#comment-16315399 ] Michael Brohl commented on OFBIZ-9147: -- Then the issue should read "Remove the exampleext plugin from the codebase" or "Move examplext functionality to example" or similar. The original intent of the provided patch (don't load exampleext OOTB ) is outdated/already solved and there is no other solution provided. Please discuss the removal in the dev list and we will take action according to the consensus, thank you. > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315398#comment-16315398 ] Jacques Le Roux commented on OFBIZ-9147: Example components (both) are there to explain/show how things works. The exampleext component is *only * there to demonstrate the extension mechanisms. It as much as simply possible does that. So usage of extension mechanisms are not blurred with other features. That's why it exists and I think it's a good thing. We previsouly had the same idea with the ecomclone component. It was removed because it was redundant with exampleext, and even more locally with ecomseo which demonstrates other usages of extension mechanisms. Now what we could do is creating an .md file where things would be more explained. This file could be used in a wiki page as an import after a Pandoc conversion to HTML, as I suggested many times and lastly today in OFBIZ-9190 > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315391#comment-16315391 ] Pierre Smits commented on OFBIZ-9147: - A cursory review of both the ofbiz-framework and ofbiz-plugins code bases will reveal that extending widgets with/from other widgets is already implemented in numerous places. Which functionality available in the exampleext component is so unique that it needs to be retained there (and can't be implemented in the example component) warranting its existence? > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10145) Remove the Gradle wrapper from our release packages and add a step to our build notes
[ https://issues.apache.org/jira/browse/OFBIZ-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315384#comment-16315384 ] Jacques Le Roux commented on OFBIZ-10145: - OK got it, WIndows users will have to download it :D. A cursory documentation should be enough. > Remove the Gradle wrapper from our release packages and add a step to our > build notes > - > > Key: OFBIZ-10145 > URL: https://issues.apache.org/jira/browse/OFBIZ-10145 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: 17.12.01 > > > Following the discussion at http://markmail.org/message/nd7grfiyobjkfwae, > considering LEGAL-288 and based on a lazy consensus on dev ML, we want to > remove the gradle-wrapper.jar file from the next packaged releases and use > [~jacopoc]'s related proposition to document how to have Gradle working in > the main README.md file. > # Extract the archive file to your local directory. > # Download gradle-wrapper.jar and place it in the > OFBiz-root-dir/gradle/wrapper folder. > I'm not sure if we should recommend a link to download the > gradle-wrapper.jar. This might change in the future (versions, etc.), so > indeed maybe simply asking to download is enough, cf > https://www.google.com/search?q=gradle-wrapper.jar+download=UTF-8 > Also we need to add a point about removing gradle-wrapper.jar in > https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9160) upgrade gradle to version 3.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315365#comment-16315365 ] Jacques Le Roux commented on OFBIZ-9160: At least testing could be done indeed > upgrade gradle to version 3.2.1 > --- > > Key: OFBIZ-9160 > URL: https://issues.apache.org/jira/browse/OFBIZ-9160 > Project: OFBiz > Issue Type: Improvement >Affects Versions: 17.12.01 >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, upgrade > > Upgrading the gradle build system to version 3.2.1 requires also upgrading > the buildbot scripts accordingly. > The proposal thread is referenced > [here|https://lists.apache.org/thread.html/4ba79bbd595f0d31f46b7402134b8392ecc5715098e93b2e5771b83f@%3Cdev.ofbiz.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-10145) Remove the Gradle wrapper from our release packages and add a step to our build notes
[ https://issues.apache.org/jira/browse/OFBIZ-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315362#comment-16315362 ] Michael Brohl edited comment on OFBIZ-10145 at 1/7/18 4:17 PM: --- Let's hope that someone using Windows will provide something similar as a batch file :-) We should do as much as possible to make it easy for users to get started. So we should provide proper documentation for a manual download/install as well as convenience scripts where possible. was (Author: mbrohl): Let's hope that someone using windows will provide something similar as a batch file :-) We should do as much as possible to make it easy for users to get started. So we should provide proper documentation for a manual download/install as well as convenience scripts where possible. > Remove the Gradle wrapper from our release packages and add a step to our > build notes > - > > Key: OFBIZ-10145 > URL: https://issues.apache.org/jira/browse/OFBIZ-10145 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: 17.12.01 > > > Following the discussion at http://markmail.org/message/nd7grfiyobjkfwae, > considering LEGAL-288 and based on a lazy consensus on dev ML, we want to > remove the gradle-wrapper.jar file from the next packaged releases and use > [~jacopoc]'s related proposition to document how to have Gradle working in > the main README.md file. > # Extract the archive file to your local directory. > # Download gradle-wrapper.jar and place it in the > OFBiz-root-dir/gradle/wrapper folder. > I'm not sure if we should recommend a link to download the > gradle-wrapper.jar. This might change in the future (versions, etc.), so > indeed maybe simply asking to download is enough, cf > https://www.google.com/search?q=gradle-wrapper.jar+download=UTF-8 > Also we need to add a point about removing gradle-wrapper.jar in > https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10145) Remove the Gradle wrapper from our release packages and add a step to our build notes
[ https://issues.apache.org/jira/browse/OFBIZ-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315362#comment-16315362 ] Michael Brohl commented on OFBIZ-10145: --- Let's hope that someone using windows will provide something similar as a batch file :-) We should do as much as possible to make it easy for users to get started. So we should provide proper documentation for a manual download/install as well as convenience scripts where possible. > Remove the Gradle wrapper from our release packages and add a step to our > build notes > - > > Key: OFBIZ-10145 > URL: https://issues.apache.org/jira/browse/OFBIZ-10145 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: 17.12.01 > > > Following the discussion at http://markmail.org/message/nd7grfiyobjkfwae, > considering LEGAL-288 and based on a lazy consensus on dev ML, we want to > remove the gradle-wrapper.jar file from the next packaged releases and use > [~jacopoc]'s related proposition to document how to have Gradle working in > the main README.md file. > # Extract the archive file to your local directory. > # Download gradle-wrapper.jar and place it in the > OFBiz-root-dir/gradle/wrapper folder. > I'm not sure if we should recommend a link to download the > gradle-wrapper.jar. This might change in the future (versions, etc.), so > indeed maybe simply asking to download is enough, cf > https://www.google.com/search?q=gradle-wrapper.jar+download=UTF-8 > Also we need to add a point about removing gradle-wrapper.jar in > https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10145) Remove the Gradle wrapper from our release packages and add a step to our build notes
[ https://issues.apache.org/jira/browse/OFBIZ-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315360#comment-16315360 ] Jacques Le Roux commented on OFBIZ-10145: - You mean something like https://github.com/apache/bigtop/blob/master/gradlew ? But then what about Windows users? > Remove the Gradle wrapper from our release packages and add a step to our > build notes > - > > Key: OFBIZ-10145 > URL: https://issues.apache.org/jira/browse/OFBIZ-10145 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: 17.12.01 > > > Following the discussion at http://markmail.org/message/nd7grfiyobjkfwae, > considering LEGAL-288 and based on a lazy consensus on dev ML, we want to > remove the gradle-wrapper.jar file from the next packaged releases and use > [~jacopoc]'s related proposition to document how to have Gradle working in > the main README.md file. > # Extract the archive file to your local directory. > # Download gradle-wrapper.jar and place it in the > OFBiz-root-dir/gradle/wrapper folder. > I'm not sure if we should recommend a link to download the > gradle-wrapper.jar. This might change in the future (versions, etc.), so > indeed maybe simply asking to download is enough, cf > https://www.google.com/search?q=gradle-wrapper.jar+download=UTF-8 > Also we need to add a point about removing gradle-wrapper.jar in > https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9160) upgrade gradle to version 3.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315349#comment-16315349 ] Michael Brohl commented on OFBIZ-9160: -- Should we not consider to upgrade Gradle to a more recent version (4.4.1 to date)? Maybe we can do it and test it coordinated with the proposed change in OFBIZ-10145. > upgrade gradle to version 3.2.1 > --- > > Key: OFBIZ-9160 > URL: https://issues.apache.org/jira/browse/OFBIZ-9160 > Project: OFBiz > Issue Type: Improvement >Affects Versions: 17.12.01 >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, upgrade > > Upgrading the gradle build system to version 3.2.1 requires also upgrading > the buildbot scripts accordingly. > The proposal thread is referenced > [here|https://lists.apache.org/thread.html/4ba79bbd595f0d31f46b7402134b8392ecc5715098e93b2e5771b83f@%3Cdev.ofbiz.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10145) Remove the Gradle wrapper from our release packages and add a step to our build notes
[ https://issues.apache.org/jira/browse/OFBIZ-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315340#comment-16315340 ] Michael Brohl commented on OFBIZ-10145: --- I think we should provide a download script like it is mentioned in the first message of the linked thread. Our users, especially those who are new to OFBiz, often have basic problems to get started and simply removing the wrapper would add more hurdles before an easy start. > Remove the Gradle wrapper from our release packages and add a step to our > build notes > - > > Key: OFBIZ-10145 > URL: https://issues.apache.org/jira/browse/OFBIZ-10145 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: 17.12.01 > > > Following the discussion at http://markmail.org/message/nd7grfiyobjkfwae, > considering LEGAL-288 and based on a lazy consensus on dev ML, we want to > remove the gradle-wrapper.jar file from the next packaged releases and use > [~jacopoc]'s related proposition to document how to have Gradle working in > the main README.md file. > # Extract the archive file to your local directory. > # Download gradle-wrapper.jar and place it in the > OFBiz-root-dir/gradle/wrapper folder. > I'm not sure if we should recommend a link to download the > gradle-wrapper.jar. This might change in the future (versions, etc.), so > indeed maybe simply asking to download is enough, cf > https://www.google.com/search?q=gradle-wrapper.jar+download=UTF-8 > Also we need to add a point about removing gradle-wrapper.jar in > https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10145) Remove the Gradle wrapper from our release packages and add a step to our build notes
[ https://issues.apache.org/jira/browse/OFBIZ-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315268#comment-16315268 ] Jacques Le Roux commented on OFBIZ-10145: - If nobody is against I'll do so before next weekend... > Remove the Gradle wrapper from our release packages and add a step to our > build notes > - > > Key: OFBIZ-10145 > URL: https://issues.apache.org/jira/browse/OFBIZ-10145 > Project: OFBiz > Issue Type: Task > Components: Gradle >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: 17.12.01 > > > Following the discussion at http://markmail.org/message/nd7grfiyobjkfwae, > considering LEGAL-288 and based on a lazy consensus on dev ML, we want to > remove the gradle-wrapper.jar file from the next packaged releases and use > [~jacopoc]'s related proposition to document how to have Gradle working in > the main README.md file. > # Extract the archive file to your local directory. > # Download gradle-wrapper.jar and place it in the > OFBiz-root-dir/gradle/wrapper folder. > I'm not sure if we should recommend a link to download the > gradle-wrapper.jar. This might change in the future (versions, etc.), so > indeed maybe simply asking to download is enough, cf > https://www.google.com/search?q=gradle-wrapper.jar+download=UTF-8 > Also we need to add a point about removing gradle-wrapper.jar in > https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10131) ID should be the abbreviation for identity in English
[ https://issues.apache.org/jira/browse/OFBIZ-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315260#comment-16315260 ] Jacques Le Roux commented on OFBIZ-10131: - Thanks James, r1820451 completed at r1820457 for AccountingErrorUiLabels.xm > ID should be the abbreviation for identity in English > - > > Key: OFBIZ-10131 > URL: https://issues.apache.org/jira/browse/OFBIZ-10131 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10131-plugins.patch, OFBIZ-10131.patch, > OFBIZ-10131.patch > > > This affects the display on the web pages. Not the naming of variables in the > codes. > Will search the *Labels.xml files and replace the word 'Id' with 'ID'. > Will also improve the logic for auto title so that labels generated for > variables like productTypeId will be 'Product Type ID' instead of 'Product > Type Id'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10131) ID should be the abbreviation for identity in English
[ https://issues.apache.org/jira/browse/OFBIZ-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315237#comment-16315237 ] James Yong commented on OFBIZ-10131: Hi Jacques, Forget to mention that I am unable to apply your patch for AccountingErrorUiLabels.xml, so the changes are missing from the commits. Can you look into it? Regards, James > ID should be the abbreviation for identity in English > - > > Key: OFBIZ-10131 > URL: https://issues.apache.org/jira/browse/OFBIZ-10131 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10131-plugins.patch, OFBIZ-10131.patch, > OFBIZ-10131.patch > > > This affects the display on the web pages. Not the naming of variables in the > codes. > Will search the *Labels.xml files and replace the word 'Id' with 'ID'. > Will also improve the logic for auto title so that labels generated for > variables like productTypeId will be 'Product Type ID' instead of 'Product > Type Id'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-10131) ID should be the abbreviation for identity in English
[ https://issues.apache.org/jira/browse/OFBIZ-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315237#comment-16315237 ] James Yong edited comment on OFBIZ-10131 at 1/7/18 12:36 PM: - Hi Jacques, Forgot to mention that I am unable to apply your patch for AccountingErrorUiLabels.xml, so the changes are missing from the commits. Can you look into it? Regards, James was (Author: jamesyong): Hi Jacques, Forget to mention that I am unable to apply your patch for AccountingErrorUiLabels.xml, so the changes are missing from the commits. Can you look into it? Regards, James > ID should be the abbreviation for identity in English > - > > Key: OFBIZ-10131 > URL: https://issues.apache.org/jira/browse/OFBIZ-10131 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10131-plugins.patch, OFBIZ-10131.patch, > OFBIZ-10131.patch > > > This affects the display on the web pages. Not the naming of variables in the > codes. > Will search the *Labels.xml files and replace the word 'Id' with 'ID'. > Will also improve the logic for auto title so that labels generated for > variables like productTypeId will be 'Product Type ID' instead of 'Product > Type Id'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-10131) ID should be the abbreviation for identity in English
[ https://issues.apache.org/jira/browse/OFBIZ-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Yong closed OFBIZ-10131. -- > ID should be the abbreviation for identity in English > - > > Key: OFBIZ-10131 > URL: https://issues.apache.org/jira/browse/OFBIZ-10131 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10131-plugins.patch, OFBIZ-10131.patch, > OFBIZ-10131.patch > > > This affects the display on the web pages. Not the naming of variables in the > codes. > Will search the *Labels.xml files and replace the word 'Id' with 'ID'. > Will also improve the logic for auto title so that labels generated for > variables like productTypeId will be 'Product Type ID' instead of 'Product > Type Id'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OFBIZ-10131) ID should be the abbreviation for identity in English
[ https://issues.apache.org/jira/browse/OFBIZ-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Yong resolved OFBIZ-10131. Resolution: Fixed The changes are now in trunk r1820450 (applied to ofbiz-plugins) & r1820451 (applied to ofbiz-framework). Thanks Jacques for the additional patches. > ID should be the abbreviation for identity in English > - > > Key: OFBIZ-10131 > URL: https://issues.apache.org/jira/browse/OFBIZ-10131 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10131-plugins.patch, OFBIZ-10131.patch, > OFBIZ-10131.patch > > > This affects the display on the web pages. Not the naming of variables in the > codes. > Will search the *Labels.xml files and replace the word 'Id' with 'ID'. > Will also improve the logic for auto title so that labels generated for > variables like productTypeId will be 'Product Type ID' instead of 'Product > Type Id'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-10131) ID should be the abbreviation for identity in English
[ https://issues.apache.org/jira/browse/OFBIZ-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309785#comment-16309785 ] James Yong edited comment on OFBIZ-10131 at 1/7/18 12:23 PM: - Sorry I didn't see the new patch. PS: So this issue is re-opened to review the new patches provided by Jacques. was (Author: jamesyong): Sorry I didn't see the new patch. > ID should be the abbreviation for identity in English > - > > Key: OFBIZ-10131 > URL: https://issues.apache.org/jira/browse/OFBIZ-10131 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10131-plugins.patch, OFBIZ-10131.patch, > OFBIZ-10131.patch > > > This affects the display on the web pages. Not the naming of variables in the > codes. > Will search the *Labels.xml files and replace the word 'Id' with 'ID'. > Will also improve the logic for auto title so that labels generated for > variables like productTypeId will be 'Product Type ID' instead of 'Product > Type Id'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315205#comment-16315205 ] Michael Brohl commented on OFBIZ-8230: -- Pierre, one of my responsibilities is to review and possibly commit contributed patches. Like you, I am free to decide on which issues I want to work. And you can easily see that I am working on a lot of issues, old and new, contributed by me and by others. I picked this issue because the latest activity was at Sept. 20th 2016, providing 2 patches. It does not seem to be actively worked on. I assigned the issue to me like we do in this case, reviewed them, asked additional questions and came to a conclusion. I did not close but expressed my conclusion here to get others to chime in and do the same. So please stop making unproductive noise and wasting someone else's time with nitpicky discussions, especially if the outcome of a review does not fit your needs or opinions. That said, I'll wait for other opinions and then take my responsibility to close this ticket accordingly in about a week. > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315195#comment-16315195 ] Pierre Smits commented on OFBIZ-8230: - We currently have about 1400 open issues, of which about 900 don't have an assignee. If a committer wants to work on issues he should start with one of those 900 first, before unilaterally deciding on issues that are assigned and the assignee is still contributing. Or else work in line of the Apache Way and seek collaboration and/or consensus. > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10028) Update Geo information according to ISO notifications
[
https://issues.apache.org/jira/browse/OFBIZ-10028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315181#comment-16315181
]
Jacques Le Roux commented on OFBIZ-10028:
-
Ecuador is in, in
trunk r1820441
R17 r1820443
Gavin added the missing hooks in svn so this should be the last Builbot test
for R17
> Update Geo information according to ISO notifications
> -
>
> Key: OFBIZ-10028
> URL: https://issues.apache.org/jira/browse/OFBIZ-10028
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Michael Brohl
>Priority: Minor
> Attachments: OFBIZ-10028_ISO_Geo_Info_Notification_CN.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_CY.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_CY.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_DE.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_EC.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_HU.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_ID.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_IS.patch
>
>
> This follows this discussion http://markmail.org/message/xn7f552qvtpua2uq,
> extract!
> bq. If someone is interested, the China changes are a bit to heavy for me,
> Here are the changes
> {quote}
> Country codes updated
> CN 2017-11-23 /China/
> CY 2017-11-23 /Cyprus/
> DE 2017-11-23 /Germany/
> EC 2017-11-23 /Ecuador/
> HK 2017-11-23 /Hong Kong/
> HU 2017-11-23 /Hungary/
> ID 2017-11-23 /Indonesia/
> IS 2017-11-23 /Iceland/
> KP 2017-11-23 /Korea (the
> Democratic People's Republic of)/
> LA 2017-11-23 /Lao
> People's Democratic Republic (the)/
> MD 2017-11-23 /Moldova
> (the Republic of)/
> MH 2017-11-23 /Marshall
> Islands (the)/
> ML 2017-11-23 /Mali/
> MO 2017-11-23 /Macao/
> MX 2017-11-23 /Mexico/
> NR 2017-11-23 /Nauru/
> PA 2017-11-23 /Panama/
> PK 2017-11-23 /Pakistan/
> QA 2017-11-23 /Qatar/
> TG 2017-11-23 /Togo/
> TJ 2017-11-23 /Tajikistan/
> UG 2017-11-23 /Uganda/
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OFBIZ-8229) Don't load demo data by default
[ https://issues.apache.org/jira/browse/OFBIZ-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-8229. Resolution: Not A Problem Assignee: Michael Brohl (was: Pierre Smits) Closing as "Not a problem" according to the opinions of 3 committers. > Don't load demo data by default > --- > > Key: OFBIZ-8229 > URL: https://issues.apache.org/jira/browse/OFBIZ-8229 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: data, operations, refactoring > Attachments: OFBIZ-8229-entityengine.xml.patch > > > Demo data loading should be a specific action. It should be loaded per > special request, not by default. In order to have adopters start with a > working OFBiz implementation, it is enough to start with loading seed and > seed-initial data only. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reassigned OFBIZ-8230: Assignee: Michael Brohl (was: Pierre Smits) > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315175#comment-16315175 ] Michael Brohl commented on OFBIZ-8230: -- Pierre, please stay constructive and don't try to produce unnecessary noise again. You complained that I am not the assignee, so I assigned the issue to me to do the next steps. I am now working on the issue as you have requested by starting a discussion to come to a conclusion to close this issue. > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9147: --- Assignee: Pierre Smits (was: Michael Brohl) > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315173#comment-16315173 ] Pierre Smits commented on OFBIZ-8230: - Reasigning the ticket to yourself without the consensus of the assignee is not the Apache Way. > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-9147. Resolution: Won't Do This is now a plugin and therefore not loaded automatically with the framework, so the problem is solved some time ago. > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-8230: --- Assignee: Pierre Smits (was: Michael Brohl) > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8229) Don't load demo data by default
[ https://issues.apache.org/jira/browse/OFBIZ-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315171#comment-16315171 ] Pierre Smits commented on OFBIZ-8229: - Reassigning tickets to yourself without consensus of the assignee is not the Apache Way. > Don't load demo data by default > --- > > Key: OFBIZ-8229 > URL: https://issues.apache.org/jira/browse/OFBIZ-8229 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: data, operations, refactoring > Attachments: OFBIZ-8229-entityengine.xml.patch > > > Demo data loading should be a specific action. It should be loaded per > special request, not by default. In order to have adopters start with a > working OFBiz implementation, it is enough to start with loading seed and > seed-initial data only. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-8229) Don't load demo data by default
[ https://issues.apache.org/jira/browse/OFBIZ-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-8229: --- Assignee: Pierre Smits (was: Michael Brohl) > Don't load demo data by default > --- > > Key: OFBIZ-8229 > URL: https://issues.apache.org/jira/browse/OFBIZ-8229 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: data, operations, refactoring > Attachments: OFBIZ-8229-entityengine.xml.patch > > > Demo data loading should be a specific action. It should be loaded per > special request, not by default. In order to have adopters start with a > working OFBiz implementation, it is enough to start with loading seed and > seed-initial data only. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reassigned OFBIZ-9147: Assignee: Michael Brohl (was: Pierre Smits) > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315169#comment-16315169 ] Jacques Le Roux commented on OFBIZ-8230: Do we really want to have a vote for such matter? It seems to me that it's abusing the Apache Way which is not procedural but prefers lasy consensus. If we can't agree, a solution is to ignore the Jira issues as long as a committer want to do something about it and especially commit. If a commit is done a veto can still be used by any committer. I'm not speaking about this issue but at large on a lot of your Jira issues which are pending for a long time with comments against them Pierre. You are not alone to decide! > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-8229) Don't load demo data by default
[ https://issues.apache.org/jira/browse/OFBIZ-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reassigned OFBIZ-8229: Assignee: Michael Brohl (was: Pierre Smits) > Don't load demo data by default > --- > > Key: OFBIZ-8229 > URL: https://issues.apache.org/jira/browse/OFBIZ-8229 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: data, operations, refactoring > Attachments: OFBIZ-8229-entityengine.xml.patch > > > Demo data loading should be a specific action. It should be loaded per > special request, not by default. In order to have adopters start with a > working OFBiz implementation, it is enough to start with loading seed and > seed-initial data only. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reassigned OFBIZ-8230: Assignee: Michael Brohl (was: Pierre Smits) > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9190) Ugrade FishEye references
[ https://issues.apache.org/jira/browse/OFBIZ-9190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315158#comment-16315158 ] Jacques Le Roux commented on OFBIZ-9190: It seem Pierre wants to "Ugrade FishEye references" in wiki, right Pierre? And it's mostly pages under https://cwiki.apache.org/confluence/display/OFBENDUSER/Base+Application+stack which was an initiative from Pierre w/o prior discussion on dev ML Because there is 10+ of them (not sure it's complete) and you have to edit each page manually it's enough to make the task tedious in Confluence :( I see 3 alternatives # Remove the whole, done :). But that would be unfortunate because Pierre put some efforts in, and especially it has value for end users! # Pierre updates the whole, done :). # A more radical change would be to put this information in svn as I suggest to most things, here .md files fits. Once that done it's a bliss to update from an IDE. But then the wikipage must be changed to import html versions of the .md files (done with Pandoc or alike). This way of doing should apply not only here but as much as we can. > Ugrade FishEye references > - > > Key: OFBIZ-9190 > URL: https://issues.apache.org/jira/browse/OFBIZ-9190 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS, site >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315152#comment-16315152 ] Pierre Smits commented on OFBIZ-8230: - Closing an improvement ticket unilaterally, while you're not the assignee, is not in line with the Apache Way. This would - at least - require a consensus of the community (or at least 3 binding votes, as this is a procedural matter). > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315147#comment-16315147 ] Michael Brohl commented on OFBIZ-9147: -- The exampleext component is there for demo purposes, like example and should be available OOTB. Looking at it, this seems to be an example on how to *extend* another component's widgets and forms and therefore has it's meaning to be a separate component. I think this should be closed as "Won't do". What do others think? > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315138#comment-16315138 ] Michael Brohl commented on OFBIZ-8230: -- Corrected. > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315132#comment-16315132 ] Michael Brohl edited comment on OFBIZ-8230 at 1/7/18 10:06 AM: --- Yes, we (or our customers) use different schemas. I see no reason to remove a working set of database resource configurations from the codebase. I'll wait another week for others to express their opinions, else close as "Won't do". If you think that the combination of different schemas has bugs, it would help the project to file an issue for it and describe the error. was (Author: mbrohl): Yes, we (or our customers) use different schemas. I see no reason to remove a working set of database resource configurations from the codebase. I'll wait another week for others to express their opinions, else close as "Not a problem". If you think that the combination of different schemas has bugs, it would help the project to file an issue for it and describe the error. > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315134#comment-16315134 ] Pierre Smits commented on OFBIZ-8230: - Closing an improvement ticket with the resolution 'Not a problem' would be a wrong choice. > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315132#comment-16315132 ] Michael Brohl commented on OFBIZ-8230: -- Yes, we (or our customers) use different schemas. I see no reason to remove a working set of database resource configurations from the codebase. I'll wait another week for others to express their opinions, else close as "Not a problem". If you think that the combination of different schemas has bugs, it would help the project to file an issue for it and describe the error. > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-7974) rename gradlew batch files to ofbiz
[ https://issues.apache.org/jira/browse/OFBIZ-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315131#comment-16315131 ] Jacques Le Roux commented on OFBIZ-7974: If you prefer, 'Won't implement' does not exist, I used 'Won't do' > rename gradlew batch files to ofbiz > --- > > Key: OFBIZ-7974 > URL: https://issues.apache.org/jira/browse/OFBIZ-7974 > Project: OFBiz > Issue Type: Improvement >Reporter: Pierre Smits >Assignee: Jacques Le Roux > > Currently we have: > * gradlew (for the unix/linux OS variants) > * gradlew.bat (for Microsoft's OS variants) > We should rename these to: > * ofbiz (for the unix/linux OS variants) > * ofbiz.bat (for Microsoft's OS variants) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-7974) rename gradlew batch files to ofbiz
[ https://issues.apache.org/jira/browse/OFBIZ-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-7974. -- Resolution: Won't Do > rename gradlew batch files to ofbiz > --- > > Key: OFBIZ-7974 > URL: https://issues.apache.org/jira/browse/OFBIZ-7974 > Project: OFBiz > Issue Type: Improvement >Reporter: Pierre Smits >Assignee: Jacques Le Roux > > Currently we have: > * gradlew (for the unix/linux OS variants) > * gradlew.bat (for Microsoft's OS variants) > We should rename these to: > * ofbiz (for the unix/linux OS variants) > * ofbiz.bat (for Microsoft's OS variants) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (OFBIZ-7974) rename gradlew batch files to ofbiz
[ https://issues.apache.org/jira/browse/OFBIZ-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reopened OFBIZ-7974: > rename gradlew batch files to ofbiz > --- > > Key: OFBIZ-7974 > URL: https://issues.apache.org/jira/browse/OFBIZ-7974 > Project: OFBiz > Issue Type: Improvement >Reporter: Pierre Smits >Assignee: Jacques Le Roux > > Currently we have: > * gradlew (for the unix/linux OS variants) > * gradlew.bat (for Microsoft's OS variants) > We should rename these to: > * ofbiz (for the unix/linux OS variants) > * ofbiz.bat (for Microsoft's OS variants) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-7974) rename gradlew batch files to ofbiz
[ https://issues.apache.org/jira/browse/OFBIZ-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315118#comment-16315118 ] Pierre Smits commented on OFBIZ-7974: - Assigning the 'Not a Problem' resolution is not a good choice. 'Won't implement' would be a better choice for improvement tickets. > rename gradlew batch files to ofbiz > --- > > Key: OFBIZ-7974 > URL: https://issues.apache.org/jira/browse/OFBIZ-7974 > Project: OFBiz > Issue Type: Improvement >Reporter: Pierre Smits >Assignee: Jacques Le Roux > > Currently we have: > * gradlew (for the unix/linux OS variants) > * gradlew.bat (for Microsoft's OS variants) > We should rename these to: > * ofbiz (for the unix/linux OS variants) > * ofbiz.bat (for Microsoft's OS variants) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315112#comment-16315112 ] Pierre Smits commented on OFBIZ-8230: - Will any adopter use more than one schema? I dare say no. Can any adopter combine 2 or more schemas with current code base? Last time I tested this it failed. So any schema other than the one used by the OFBiz project (derby) is example/referential info. And thus it should not be in the code base but in documentation... > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9147) Disentangle ExampleExt from the codebase
[ https://issues.apache.org/jira/browse/OFBIZ-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315111#comment-16315111 ] Pierre Smits commented on OFBIZ-9147: - This patch addresses the automatically loading of the component. What the plan of the project is regarding the component is not up to me. As soon as there is a clarity I can, and if time permits, further actions. > Disentangle ExampleExt from the codebase > > > Key: OFBIZ-9147 > URL: https://issues.apache.org/jira/browse/OFBIZ-9147 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: refactoring > Attachments: OFBIZ-9147-component-load.xml.patch > > > Currently the functionality of the ExampleExt component brings nothing more > than a few widgets that extend the examples in the Example component. These > ExampleExt widgets can as easily exist in the Example component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
