[jira] [Comment Edited] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505450#comment-15505450 ] Taher Alkhateeb edited comment on OFBIZ-8293 at 9/20/16 3:26 AM: - Hello .. RTL guy here :) I used flatgrey because it is the most well supported RTL theme. However, it would be great at some point to reduce themes and make them all RTL enabled. As I mentioned elsewhere the widgets and themes are in need of a major overhaul. was (Author: taher): Hello .. RTL guy here :) I used flatgray because it is the most well supported RTL theme. However, it would be great at some point to reduce themes and make them all RTL enabled. As I mentioned elsewhere the widgets and themes are in need of a major overhaul. > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB backend themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: > # bizzness time, still not complete after several years see OFBIZ-2398 > # BlueLight, it's subsumed by Tomahawk which is the last variant of this > group and more complete > # Dropping Crumbs, it's subsumed by Tomahawk which is the last variant of > this group and more complete > # 3 instances of Rainbow Stone, we need to collectively decide which ones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505450#comment-15505450 ] Taher Alkhateeb commented on OFBIZ-8293: Hello .. RTL guy here :) I used flatgray because it is the most well supported RTL theme. However, it would be great at some point to reduce themes and make them all RTL enabled. As I mentioned elsewhere the widgets and themes are in need of a major overhaul. > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB backend themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: > # bizzness time, still not complete after several years see OFBIZ-2398 > # BlueLight, it's subsumed by Tomahawk which is the last variant of this > group and more complete > # Dropping Crumbs, it's subsumed by Tomahawk which is the last variant of > this group and more complete > # 3 instances of Rainbow Stone, we need to collectively decide which ones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6300) Compiler-Error with JDK 1.8 and source compatibility 1.8
[ https://issues.apache.org/jira/browse/OFBIZ-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-6300. Resolution: Fixed Fix Version/s: Release Branch 13.07 Also backported to release branch 13.07 r1761504. > Compiler-Error with JDK 1.8 and source compatibility 1.8 > > > Key: OFBIZ-6300 > URL: https://issues.apache.org/jira/browse/OFBIZ-6300 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Martin Becker >Assignee: Michael Brohl > Fix For: Release Branch 14.12, Release Branch 13.07, 15.12.01 > > Attachments: OFBIZ-6300-EntityFieldMap.patch > > > I just found another error compiling the code with JDK 1.8 with source code > compatibility switched to 1.8 in my eclipse workspace. The external ant build > is working because there is java version 1.7 defined as target in the > macros.xml. > The error is an issue regarding generics in EntityFieldMap.java. > I will provide a patch her soon. > The code is the same in the release branches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (OFBIZ-6300) Compiler-Error with JDK 1.8 and source compatibility 1.8
[ https://issues.apache.org/jira/browse/OFBIZ-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reopened OFBIZ-6300: -- Reopen for another backport. > Compiler-Error with JDK 1.8 and source compatibility 1.8 > > > Key: OFBIZ-6300 > URL: https://issues.apache.org/jira/browse/OFBIZ-6300 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Martin Becker >Assignee: Michael Brohl > Fix For: Release Branch 14.12, 15.12.01 > > Attachments: OFBIZ-6300-EntityFieldMap.patch > > > I just found another error compiling the code with JDK 1.8 with source code > compatibility switched to 1.8 in my eclipse workspace. The external ant build > is working because there is java version 1.7 defined as target in the > macros.xml. > The error is an issue regarding generics in EntityFieldMap.java. > I will provide a patch her soon. > The code is the same in the release branches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8223) Broken page renders while click on Submit button on Qualification Screen
[ https://issues.apache.org/jira/browse/OFBIZ-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504656#comment-15504656 ] Michael Brohl commented on OFBIZ-8223: -- Yes, according to Sharans announcement the sprint is open until Tuesday morning. > Broken page renders while click on Submit button on Qualification Screen > > > Key: OFBIZ-8223 > URL: https://issues.apache.org/jira/browse/OFBIZ-8223 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Avnindra Sharma >Assignee: Michael Brohl >Priority: Minor > Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming > Branch, Release Branch 15.12 > > Attachments: OFBIZ-8223.patch > > > Steps to reproduce: > 1. Go to party manager. > 2. Find party Company and navigate to Qualification tab. > 3. Now if there is no existing application and Submit button visible then > click on submit button. > 4. Broken page renders with error message " > :ERROR MESSAGE: > org.ofbiz.webapp.event.EventHandlerException: No rows to process" > Ideally system should hide submit button if there is no application to > process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7895) ebay : Remove unused imports from groovy files.
[ https://issues.apache.org/jira/browse/OFBIZ-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-7895. > ebay : Remove unused imports from groovy files. > --- > > Key: OFBIZ-7895 > URL: https://issues.apache.org/jira/browse/OFBIZ-7895 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/ebay >Affects Versions: Trunk >Reporter: Ankit Joshi >Assignee: Michael Brohl >Priority: Minor > Fix For: 14.12.01, Upcoming Branch, 15.12.01 > > Attachments: OFBIZ-7895-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-8033) Lucene : Remove unused imports from groovy files for code optimization.
[ https://issues.apache.org/jira/browse/OFBIZ-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-8033. > Lucene : Remove unused imports from groovy files for code optimization. > > > Key: OFBIZ-8033 > URL: https://issues.apache.org/jira/browse/OFBIZ-8033 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/lucene >Affects Versions: Trunk >Reporter: Ankit Joshi >Assignee: Michael Brohl >Priority: Minor > Fix For: 14.12.01, Upcoming Branch, 15.12.01 > > Attachments: OFBIZ-8033_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-8032) AssetMaint : Remove unused imports from groovy files for code optimization.
[ https://issues.apache.org/jira/browse/OFBIZ-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-8032. > AssetMaint : Remove unused imports from groovy files for code optimization. > --- > > Key: OFBIZ-8032 > URL: https://issues.apache.org/jira/browse/OFBIZ-8032 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/assetmaint >Affects Versions: Trunk >Reporter: Ankit Joshi >Assignee: Michael Brohl >Priority: Minor > Fix For: 14.12.01, Upcoming Branch, 15.12.01 > > Attachments: OFBIZ-8032_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-8034) Passport : Remove unused imports from groovy files for code optimization.
[ https://issues.apache.org/jira/browse/OFBIZ-8034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-8034. > Passport : Remove unused imports from groovy files for code optimization. > - > > Key: OFBIZ-8034 > URL: https://issues.apache.org/jira/browse/OFBIZ-8034 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/passport >Affects Versions: Trunk >Reporter: Ankit Joshi >Assignee: Michael Brohl >Priority: Minor > Fix For: 14.12.01, Upcoming Branch, 15.12.01 > > Attachments: OFBIZ-8034_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8223) Broken page renders while click on Submit button on Qualification Screen
[ https://issues.apache.org/jira/browse/OFBIZ-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504622#comment-15504622 ] Jacques Le Roux commented on OFBIZ-8223: Do we still sprint? > Broken page renders while click on Submit button on Qualification Screen > > > Key: OFBIZ-8223 > URL: https://issues.apache.org/jira/browse/OFBIZ-8223 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Avnindra Sharma >Assignee: Michael Brohl >Priority: Minor > Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming > Branch, Release Branch 15.12 > > Attachments: OFBIZ-8223.patch > > > Steps to reproduce: > 1. Go to party manager. > 2. Find party Company and navigate to Qualification tab. > 3. Now if there is no existing application and Submit button visible then > click on submit button. > 4. Broken page renders with error message " > :ERROR MESSAGE: > org.ofbiz.webapp.event.EventHandlerException: No rows to process" > Ideally system should hide submit button if there is no application to > process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7970) Reorder the component loading in the application stack
[ https://issues.apache.org/jira/browse/OFBIZ-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-7970: - Sprint: Community Day 3 - 2016 > Reorder the component loading in the application stack > -- > > Key: OFBIZ-7970 > URL: https://issues.apache.org/jira/browse/OFBIZ-7970 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Trivial > Attachments: OFBIZ-7970-component-load.xml-v2.patch, > OFBIZ-7970-component-load.xml.patch > > > While working on the demo data in the ecommerce component, I noticed that the > order of components in the application stack could be improved to bring it > more in line with some business conventions with respect to ERP > implementations. > This is related to OFBIZ-7016 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7415) Move 3rd party payment integrations from accounting application to seppcialpurpose
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-7415: --- Summary: Move 3rd party payment integrations from accounting application to seppcialpurpose (was: Move 3rd party payment integrations from accounting application to sepcialpurpose) > Move 3rd party payment integrations from accounting application to > seppcialpurpose > -- > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Mridul Pathak > Attachments: OFBIZ_7415.patch > > > This is a placeholder issue to capture all sub tasks for removing 3rd party > payment integrations from accounting application and moving to a new > component in special purpose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-8223) Broken page renders while click on Submit button on Qualification Screen
[ https://issues.apache.org/jira/browse/OFBIZ-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-8223. Resolution: Fixed > Broken page renders while click on Submit button on Qualification Screen > > > Key: OFBIZ-8223 > URL: https://issues.apache.org/jira/browse/OFBIZ-8223 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Avnindra Sharma >Assignee: Michael Brohl >Priority: Minor > Fix For: Upcoming Branch, Release Branch 15.12, Release Branch > 14.12, Release Branch 13.07 > > Attachments: OFBIZ-8223.patch > > > Steps to reproduce: > 1. Go to party manager. > 2. Find party Company and navigate to Qualification tab. > 3. Now if there is no existing application and Submit button visible then > click on submit button. > 4. Broken page renders with error message " > :ERROR MESSAGE: > org.ofbiz.webapp.event.EventHandlerException: No rows to process" > Ideally system should hide submit button if there is no application to > process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8223) Broken page renders while click on Submit button on Qualification Screen
[ https://issues.apache.org/jira/browse/OFBIZ-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-8223: - Sprint: Community Day 3 - 2016 > Broken page renders while click on Submit button on Qualification Screen > > > Key: OFBIZ-8223 > URL: https://issues.apache.org/jira/browse/OFBIZ-8223 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Avnindra Sharma >Assignee: Michael Brohl >Priority: Minor > Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming > Branch, Release Branch 15.12 > > Attachments: OFBIZ-8223.patch > > > Steps to reproduce: > 1. Go to party manager. > 2. Find party Company and navigate to Qualification tab. > 3. Now if there is no existing application and Submit button visible then > click on submit button. > 4. Broken page renders with error message " > :ERROR MESSAGE: > org.ofbiz.webapp.event.EventHandlerException: No rows to process" > Ideally system should hide submit button if there is no application to > process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-8265) Bursted Layout in screen "orderstatus" of ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-8265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504579#comment-15504579 ] Jacques Le Roux edited comment on OFBIZ-8265 at 9/19/16 8:20 PM: - Thanks fumiyoshi.to, After review I agree it's the right way to fix. OrderStatus.ftl indirectly calls OrderItems.ftl through the orderitems screen so nothing is lost when the addCommonToCartForm is moved from OrderStatus.ftl to OrderItems.ft, it's only a rearrangement which fixes the issue, well spotted! Your patch is in trunk r1761431 R15.12, 14.12, 13.07 r1761497 was (Author: jacques.le.roux): Thanks fumiyoshi.to, Your patch is in trunk r1761431 R15.12, 14.12, 13.07 r1761497 > Bursted Layout in screen "orderstatus" of ecommerce > --- > > Key: OFBIZ-8265 > URL: https://issues.apache.org/jira/browse/OFBIZ-8265 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/ecommerce >Affects Versions: Trunk > Environment: FireFox48.0.2 > Internet Explore 11 >Reporter: fumiyoshi.to >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming > Branch, Release Branch 15.12 > > Attachments: OFBIZ-8265_BurstedLayoutInOrderStatusOfEcommerce.patch, > screenshot-1.png, screenshot-2.png > > > The layout of screen "order status" of application "ecommerce" is bursted . > URL: https://localhost:8443/ecommerce/control/orderstatus?orderId=WSCO1 > I save the html of the screen into my local file, and It works fine. > I don't know the reason exactly, but the patch attached by me works > correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8223) Broken page renders while click on Submit button on Qualification Screen
[ https://issues.apache.org/jira/browse/OFBIZ-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-8223: - Affects Version/s: Release Branch 13.07 Release Branch 14.12 Trunk Release Branch 15.12 > Broken page renders while click on Submit button on Qualification Screen > > > Key: OFBIZ-8223 > URL: https://issues.apache.org/jira/browse/OFBIZ-8223 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Avnindra Sharma >Assignee: Michael Brohl >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-8223.patch > > > Steps to reproduce: > 1. Go to party manager. > 2. Find party Company and navigate to Qualification tab. > 3. Now if there is no existing application and Submit button visible then > click on submit button. > 4. Broken page renders with error message " > :ERROR MESSAGE: > org.ofbiz.webapp.event.EventHandlerException: No rows to process" > Ideally system should hide submit button if there is no application to > process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-8028) OFBIZ-7649: Display From date with default now() on all screens under Accounting Application
[ https://issues.apache.org/jira/browse/OFBIZ-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah closed OFBIZ-8028. --- Validated the fixes and found them working as expected > OFBIZ-7649: Display From date with default now() on all screens under > Accounting Application > > > Key: OFBIZ-8028 > URL: https://issues.apache.org/jira/browse/OFBIZ-8028 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Ratnesh Upadhyay >Assignee: Swapnil Shah > Attachments: OFBIZ-8028.patch > > > Display From date with default now() on all screens under Accounting > Application. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7666) OFBIZ-7649: Display From date with default now() on all screens under Project Application
[ https://issues.apache.org/jira/browse/OFBIZ-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah closed OFBIZ-7666. --- Validated the fixes and found them working as expected > OFBIZ-7649: Display From date with default now() on all screens under Project > Application > - > > Key: OFBIZ-7666 > URL: https://issues.apache.org/jira/browse/OFBIZ-7666 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: 14.12.01, 15.12.01 >Reporter: Swapnil Shah >Assignee: Swapnil Shah > Attachments: OFBIZ-7666.patch > > > To begin with can start fixing it under > # > https://ofbiz-vm.apache.org:8443/projectmgr/control/ListWorkEffortPartyAssigns?projectId=9000 > # > https://ofbiz-vm.apache.org:8443/projectmgr/control/EditTaskPartyAssigns?workEffortId=9106 > # > https://ofbiz-vm.apache.org:8443/projectmgr/control/EditWorkEffortSurveyAppls?workEffortId=9106 > # > https://ofbiz-vm.apache.org:8443/projectmgr/control/listResourcesProject?partyId=admin > # > https://ofbiz-vm.apache.org:8443/projectmgr/control/listResourcesTask?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7665) OFBIZ-7649: Display From date with default now() on all screens under Content Application
[ https://issues.apache.org/jira/browse/OFBIZ-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah closed OFBIZ-7665. --- Validated the fixes and found them working as expected > OFBIZ-7649: Display From date with default now() on all screens under Content > Application > - > > Key: OFBIZ-7665 > URL: https://issues.apache.org/jira/browse/OFBIZ-7665 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: 14.12.01, 15.12.01 >Reporter: Swapnil Shah >Assignee: Swapnil Shah > Attachments: OFBIZ-7665.patch > > > To begin with can start fixing it under > # > https://ofbiz-vm.apache.org:8443/content/control/ListWebSiteContent?webSiteId=WebStore > # https://ofbiz-vm.apache.org:8443/content/control/createWebSiteContactList > # > https://ofbiz-vm.apache.org:8443/content/control/findForums?forumGroupId=WebStoreFORUM > # > https://ofbiz-vm.apache.org:8443/content/control/forumGroupRoles?forumGroupId=WebStoreFORUM > # > https://ofbiz-vm.apache.org:8443/content/control/EditContentRole?contentId=BLOGROOTBIGAL > # > https://ofbiz-vm.apache.org:8443/content/control/EditContentAssoc?contentId=BLOGROOTBIGAL > # > https://ofbiz-vm.apache.org:8443/content/control/EditContentWorkEfforts?contentId=BLOGROOTBIGAL > # > https://ofbiz-vm.apache.org:8443/content/control/EditDataResourceRole?dataResourceId=STDWRAP001 > # https://ofbiz-vm.apache.org:8443/content/control/EditAddContenta -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504149#comment-15504149 ] Pierre Smits commented on OFBIZ-8293: - And flatgrey. > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB backend themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: > # bizzness time, still not complete after several years see OFBIZ-2398 > # BlueLight, it's subsumed by Tomahawk which is the last variant of this > group and more complete > # Dropping Crumbs, it's subsumed by Tomahawk which is the last variant of > this group and more complete > # 3 instances of Rainbow Stone, we need to collectively decide which ones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7073) Add WebSocket support in OFBiz
[
https://issues.apache.org/jira/browse/OFBIZ-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503627#comment-15503627
]
Amardeep Singh Jhajj commented on OFBIZ-7073:
-
WebSocket support was not working after upgrade of trunk to gradle. I have
slightly change the FilterJar.java to scan the appropriate jar, it is working
now. Please find attached patch for it. Once this is committed, I will add wiki
page for WebSocket usage.
> Add WebSocket support in OFBiz
> --
>
> Key: OFBIZ-7073
> URL: https://issues.apache.org/jira/browse/OFBIZ-7073
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Affects Versions: Trunk
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7073.patch, OFBIZ-7073.patch,
> tomcat-embed-websocket-8.0.33.jar
>
>
> I tried to use websockets in OFBiz. I simply added tomcat-embed-websocket.jar
> in catalina lib and created one webapp for websocket and also added server
> endpoint class.
> It didn't work. After that, I tried the same thing with plain j2ee
> application with embedded tomcat. It worked there.
> I researched on above issue in OFBiz and got the reason. Websockets
> implementation need jar scanning enabled and it is currently disabled in
> OFBiz. Below is the code snippet of disabling jar scan from
> CatalinaContainer.java:
> {code}
> JarScanner jarScanner = context.getJarScanner();
> if (jarScanner instanceof StandardJarScanner) {
> StandardJarScanner standardJarScanner = (StandardJarScanner) jarScanner;
> standardJarScanner.setScanClassPath(false);
> }
> {code}
> Jar scanning enabling increase OFBiz server startup time upto couples of
> minutes (in my case, it took approx 8 minutes), so we don't want this much of
> startup time for OFBiz.
>
> I got the following document where I found the reason why websocket is not
> working if scanning disabled.
> https://wiki.apache.org/tomcat/HowTo/FasterStartUp
> Here tips are given to decrease the startup time. This tips also include
> disabling of jar scanning.
> We can say disabling jar scanning is right approach because if we enable it
> then scanner will scan all the jars loaded in OFBiz startup that we don't
> want.
> But, If we want websockets working then we have to enable jar scanning.
> For enabling jar scanning, we need below code:
> {code}
> standardJarScanner.setScanClassPath(true); // Will increase server startup
> time.
> {code}
> Solution: We can add filter on jar scanning. It will allow only some kind of
> jars only. For example: jars having websockets endpoints. I am attaching
> patch for the same here.
> I added filter like if jar name string contains "discoverable" word then only
> it will be considered for jar scan. We can change jar name of our jars using
> build.xml to make it discoverable for jar scanning.
> For example: I have added my websocket endpoint class in
> "specialpurpose/ecommerce/src" and changed the "name" property in build.xml
> of ecommerce component from "ofbiz-ecommerce"
> to "ofbiz-ecommerce-discoverable". Here is the code snippet from build.xml:
> {code}
>
> {code}
> This change will create the jar with name "ofbiz-ecommerce-discoverable.jar"
> in "ecommerce/build/lib/".
> Now created jar will be scanned in jar scanner as its name contains
> "discoverable" word in it.
> This change will not increase server start up time more than couple of
> seconds (in my case, it just two seconds). So scanning time totally depends
> on the list of jars scanned.
> Conclusion: We can use websocket support with the help of jar filters.
> I am also attaching the version 8.0.33 tomcat-embed-websocket.jar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-7073) Add WebSocket support in OFBiz
[
https://issues.apache.org/jira/browse/OFBIZ-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amardeep Singh Jhajj updated OFBIZ-7073:
Attachment: OFBIZ-7073.patch
> Add WebSocket support in OFBiz
> --
>
> Key: OFBIZ-7073
> URL: https://issues.apache.org/jira/browse/OFBIZ-7073
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Affects Versions: Trunk
>Reporter: Amardeep Singh Jhajj
>Assignee: Amardeep Singh Jhajj
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7073.patch, OFBIZ-7073.patch,
> tomcat-embed-websocket-8.0.33.jar
>
>
> I tried to use websockets in OFBiz. I simply added tomcat-embed-websocket.jar
> in catalina lib and created one webapp for websocket and also added server
> endpoint class.
> It didn't work. After that, I tried the same thing with plain j2ee
> application with embedded tomcat. It worked there.
> I researched on above issue in OFBiz and got the reason. Websockets
> implementation need jar scanning enabled and it is currently disabled in
> OFBiz. Below is the code snippet of disabling jar scan from
> CatalinaContainer.java:
> {code}
> JarScanner jarScanner = context.getJarScanner();
> if (jarScanner instanceof StandardJarScanner) {
> StandardJarScanner standardJarScanner = (StandardJarScanner) jarScanner;
> standardJarScanner.setScanClassPath(false);
> }
> {code}
> Jar scanning enabling increase OFBiz server startup time upto couples of
> minutes (in my case, it took approx 8 minutes), so we don't want this much of
> startup time for OFBiz.
>
> I got the following document where I found the reason why websocket is not
> working if scanning disabled.
> https://wiki.apache.org/tomcat/HowTo/FasterStartUp
> Here tips are given to decrease the startup time. This tips also include
> disabling of jar scanning.
> We can say disabling jar scanning is right approach because if we enable it
> then scanner will scan all the jars loaded in OFBiz startup that we don't
> want.
> But, If we want websockets working then we have to enable jar scanning.
> For enabling jar scanning, we need below code:
> {code}
> standardJarScanner.setScanClassPath(true); // Will increase server startup
> time.
> {code}
> Solution: We can add filter on jar scanning. It will allow only some kind of
> jars only. For example: jars having websockets endpoints. I am attaching
> patch for the same here.
> I added filter like if jar name string contains "discoverable" word then only
> it will be considered for jar scan. We can change jar name of our jars using
> build.xml to make it discoverable for jar scanning.
> For example: I have added my websocket endpoint class in
> "specialpurpose/ecommerce/src" and changed the "name" property in build.xml
> of ecommerce component from "ofbiz-ecommerce"
> to "ofbiz-ecommerce-discoverable". Here is the code snippet from build.xml:
> {code}
>
> {code}
> This change will create the jar with name "ofbiz-ecommerce-discoverable.jar"
> in "ecommerce/build/lib/".
> Now created jar will be scanned in jar scanner as its name contains
> "discoverable" word in it.
> This change will not increase server start up time more than couple of
> seconds (in my case, it just two seconds). So scanning time totally depends
> on the list of jars scanned.
> Conclusion: We can use websocket support with the help of jar filters.
> I am also attaching the version 8.0.33 tomcat-embed-websocket.jar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-8295) Convert removeDataCategory service from simple to entity-auto
[ https://issues.apache.org/jira/browse/OFBIZ-8295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-8295: --- Attachment: OFBIZ-8295.patch Attaching patch for this improvement. I have converted service engine to entity-auto from simple and removed service implementation. > Convert removeDataCategory service from simple to entity-auto > - > > Key: OFBIZ-8295 > URL: https://issues.apache.org/jira/browse/OFBIZ-8295 > Project: OFBiz > Issue Type: Improvement > Components: content >Affects Versions: Trunk >Reporter: Pawan Verma > Attachments: OFBIZ-8295.patch > > > Convert removeDataCategory service from simple to entity-auto as it is simply > updated data category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8294) Convert updateDataCategory service from simple to entity-auto
[ https://issues.apache.org/jira/browse/OFBIZ-8294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-8294: --- Attachment: OFBIZ-8294.patch Attaching patch for this improvement. I have converted service engine to entity-auto from simple and removed service implementation. > Convert updateDataCategory service from simple to entity-auto > - > > Key: OFBIZ-8294 > URL: https://issues.apache.org/jira/browse/OFBIZ-8294 > Project: OFBiz > Issue Type: Improvement > Components: content >Affects Versions: Trunk >Reporter: Pawan Verma > Attachments: OFBIZ-8294.patch > > > Convert updateDataCategory service from simple to entity-auto as it is simply > updated data category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8243) End date calculation of workefforts is wrong
[ https://issues.apache.org/jira/browse/OFBIZ-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-8243: Priority: Major (was: Blocker) > End date calculation of workefforts is wrong > > > Key: OFBIZ-8243 > URL: https://issues.apache.org/jira/browse/OFBIZ-8243 > Project: OFBiz > Issue Type: Bug > Components: manufacturing, workeffort >Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12 > Environment: This happens in following setups: > R15.12 against MySQL > R15.12 against PostgreSQL > It does not happen in setup: > R15.12 against Derby. >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: productionrun, routing > Attachments: Screen Shot 2016-09-14 at 08.33.10.png > > > When a new production run is generated based on a production schema with > tasks, the process takes the tasks of the schema (in the designated order) > and calculate the start and end date for each task (based on the provided > start date of the production run. > This process doesn't work properly as tasks with a total throughput time > (setup + run time) more than 1 day leads to wrong results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8294) Convert updateDataCategory service from simple to entity-auto
Pawan Verma created OFBIZ-8294: -- Summary: Convert updateDataCategory service from simple to entity-auto Key: OFBIZ-8294 URL: https://issues.apache.org/jira/browse/OFBIZ-8294 Project: OFBiz Issue Type: Improvement Components: content Affects Versions: Trunk Reporter: Pawan Verma Convert updateDataCategory service from simple to entity-auto as it is simply updated data category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8243) End date calculation of workefforts is wrong
[ https://issues.apache.org/jira/browse/OFBIZ-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-8243: Environment: This happens in following setups: R15.12 against MySQL R15.12 against PostgreSQL It does not happen in setup: R15.12 against Derby. > End date calculation of workefforts is wrong > > > Key: OFBIZ-8243 > URL: https://issues.apache.org/jira/browse/OFBIZ-8243 > Project: OFBiz > Issue Type: Bug > Components: manufacturing, workeffort >Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12 > Environment: This happens in following setups: > R15.12 against MySQL > R15.12 against PostgreSQL > It does not happen in setup: > R15.12 against Derby. >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: productionrun, routing > Attachments: Screen Shot 2016-09-14 at 08.33.10.png > > > When a new production run is generated based on a production schema with > tasks, the process takes the tasks of the schema (in the designated order) > and calculate the start and end date for each task (based on the provided > start date of the production run. > This process doesn't work properly as tasks with a total throughput time > (setup + run time) more than 1 day leads to wrong results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503160#comment-15503160 ] Jacques Le Roux edited comment on OFBIZ-8293 at 9/19/16 11:34 AM: -- If we need votes, let's go. I think we need at least one for removing "3 instances of Rainbow Stone" anyway was (Author: jacques.le.roux): If we need votes, let's go. I think xe need at least one for removing "3 instances of Rainbow Stone" anyway > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB backend themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: > # bizzness time, still not complete after several years see OFBIZ-2398 > # BlueLight, it's subsumed by Tomahawk which is the last variant of this > group and more complete > # Dropping Crumbs, it's subsumed by Tomahawk which is the last variant of > this group and more complete > # 3 instances of Rainbow Stone, we need to collectively decide which ones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503160#comment-15503160 ] Jacques Le Roux commented on OFBIZ-8293: If we need votes, let's go. I think xe need at least one for removing "3 instances of Rainbow Stone" anyway > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB backend themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: > # bizzness time, still not complete after several years see OFBIZ-2398 > # BlueLight, it's subsumed by Tomahawk which is the last variant of this > group and more complete > # Dropping Crumbs, it's subsumed by Tomahawk which is the last variant of > this group and more complete > # 3 instances of Rainbow Stone, we need to collectively decide which ones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503156#comment-15503156 ] Jacques Le Roux commented on OFBIZ-8293: Here are some discussions you find when looking for "remove theme", I think here we really need a new fresh start and not look back. http://markmail.org/message/boqhok57dzp3zwpe http://markmail.org/message/34z2a4n3nzymv3bu http://markmail.org/message/ovdjzmlwn2udqvpm http://markmail.org/message/lu6uy67oqkydedvl http://markmail.org/thread/lu6uy67oqkydedvl We can find much more related discussion, but nothing happened, it's time! > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB backend themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: > # bizzness time, still not complete after several years see OFBIZ-2398 > # BlueLight, it's subsumed by Tomahawk which is the last variant of this > group and more complete > # Dropping Crumbs, it's subsumed by Tomahawk which is the last variant of > this group and more complete > # 3 instances of Rainbow Stone, we need to collectively decide which ones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503142#comment-15503142 ] Jacques Le Roux edited comment on OFBIZ-8293 at 9/19/16 11:24 AM: -- You were too fast with your comment, we crossed online :) I'll look for the discussions on the dev ML... was (Author: jacques.le.roux): You were too fast with your comment, we crossed online :) I'll look for the discussion on the dev ML... > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB backend themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: > # bizzness time, still not complete after several years see OFBIZ-2398 > # BlueLight, it's subsumed by Tomahawk which is the last variant of this > group and more complete > # Dropping Crumbs, it's subsumed by Tomahawk which is the last variant of > this group and more complete > # 3 instances of Rainbow Stone, we need to collectively decide which ones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-8293: --- Description: We already already discussed several times on dev ML to reduce the number of OOTB backend themes and we globally agreed about doing so. These themes are still working so we will move them to Attic from where (using svn history) they can be fetch to create expected plugins (tough I'm not sure we can yet create theme-plugins but this is expected) If nobody disagree I'll do so in few days... BTW the themes I expect to remove in a 1st phase are: # bizzness time, still not complete after several years see OFBIZ-2398 # BlueLight, it's subsumed by Tomahawk which is the last variant of this group and more complete # Dropping Crumbs, it's subsumed by Tomahawk which is the last variant of this group and more complete # 3 instances of Rainbow Stone, we need to collectively decide which ones was: We already already discussed several times on dev ML to reduce the number of OOTB backend themes and we globally agreed about doing so. These themes are still working so we will move them to Attic from where (using svn history) they can be fetch to create expected plugins (tough I'm not sure we can yet create theme-plugins but this is expected) If nobody disagree I'll do so in few days... BTW the themes I expect to remove in a 1st phase are: # bizzness time, still not complete after several years see OFBIZ-2398 # BlueLight, it's subsumed by Tomahawk which the last variants and more complete # Dropping Crumbs, it's subsumed by Tomahawk which the last variants and more complete # 3 instances of Rainbow Stone, we need to collectively decide which ones > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB backend themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: > # bizzness time, still not complete after several years see OFBIZ-2398 > # BlueLight, it's subsumed by Tomahawk which is the last variant of this > group and more complete > # Dropping Crumbs, it's subsumed by Tomahawk which is the last variant of > this group and more complete > # 3 instances of Rainbow Stone, we need to collectively decide which ones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503142#comment-15503142 ] Jacques Le Roux commented on OFBIZ-8293: You were too fast with your comment, we crossed online :) I'll look for the discussion on the dev ML... > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB backend themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: > # bizzness time, still not complete after several years see OFBIZ-2398 > # BlueLight, it's subsumed by Tomahawk which the last variants and more > complete > # Dropping Crumbs, it's subsumed by Tomahawk which the last variants and more > complete > # 3 instances of Rainbow Stone, we need to collectively decide which ones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-8293: --- Description: We already already discussed several times on dev ML to reduce the number of OOTB backend themes and we globally agreed about doing so. These themes are still working so we will move them to Attic from where (using svn history) they can be fetch to create expected plugins (tough I'm not sure we can yet create theme-plugins but this is expected) If nobody disagree I'll do so in few days... BTW the themes I expect to remove in a 1st phase are: # bizzness time, still not complete after several years see OFBIZ-2398 # BlueLight, it's subsumed by Tomahawk which the last variants and more complete # Dropping Crumbs, it's subsumed by Tomahawk which the last variants and more complete # 3 instances of Rainbow Stone, we need to collectively decide which ones was: We already already discussed several times on dev ML to reduce the number of OOTB themes and we globally agreed about doing so. These themes are still working so we will move them to Attic from where (using svn history) they can be fetch to create expected plugins (tough I'm not sure we can yet create theme-plugins but this is expected) If nobody disagree I'll do so in few days... BTW the themes I expect to remove in a 1st phase are: > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB backend themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: > # bizzness time, still not complete after several years see OFBIZ-2398 > # BlueLight, it's subsumed by Tomahawk which the last variants and more > complete > # Dropping Crumbs, it's subsumed by Tomahawk which the last variants and more > complete > # 3 instances of Rainbow Stone, we need to collectively decide which ones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503129#comment-15503129 ] Pierre Smits commented on OFBIZ-8293: - [~jacques.le.roux] Could you please include the mail thread(s) in which this was discussed. Also, could you please list the themes which were agreed upon to get disentangled from trunk? Otherwise this issue is very cryptic. > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8293) Remove redundant backend themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-8293: --- Summary: Remove redundant backend themes (was: Remove redundant themes) > Remove redundant backend themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8293) Remove redundant themes
[ https://issues.apache.org/jira/browse/OFBIZ-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-8293: --- Description: We already already discussed several times on dev ML to reduce the number of OOTB themes and we globally agreed about doing so. These themes are still working so we will move them to Attic from where (using svn history) they can be fetch to create expected plugins (tough I'm not sure we can yet create theme-plugins but this is expected) If nobody disagree I'll do so in few days... BTW the themes I expect to remove in a 1st phase are: was: We already already discussed several times on dev ML to reduce the number of OOTB themes and we globally agreed about doing so. These themes are still working so we will move them to Attic from where (using svn history) they can be fetch to create expected plugins (tough I'm not sure we can yet create theme-plugins but this is expected) If nobody disagree I'll do so in few days... > Remove redundant themes > --- > > Key: OFBIZ-8293 > URL: https://issues.apache.org/jira/browse/OFBIZ-8293 > Project: OFBiz > Issue Type: Improvement > Components: themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > We already already discussed several times on dev ML to reduce the number of > OOTB themes and we globally agreed about doing so. > These themes are still working so we will move them to Attic from where > (using svn history) they can be fetch to create expected plugins (tough I'm > not sure we can yet create theme-plugins but this is expected) > If nobody disagree I'll do so in few days... > BTW the themes I expect to remove in a 1st phase are: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6466) Lookup modal window is overlapped by top menu
[ https://issues.apache.org/jira/browse/OFBIZ-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6466. -- Resolution: Not A Problem Since the Boostrap seems to have been abandonned this issues no longer stands > Lookup modal window is overlapped by top menu > - > > Key: OFBIZ-6466 > URL: https://issues.apache.org/jira/browse/OFBIZ-6466 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Bootstrap theme >Reporter: Pierre Smits > Attachments: Screen Shot 2015-06-06 at 14.30.50.png > > > When opening a lookup window (modal window) the top menu is on top of the > modal window. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6437) Drop-down menus should be defined explicitly
[
https://issues.apache.org/jira/browse/OFBIZ-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-6437.
--
Resolution: Not A Problem
Since the Boostrap seems to have been abandonned this issues no longer stands
> Drop-down menus should be defined explicitly
>
>
> Key: OFBIZ-6437
> URL: https://issues.apache.org/jira/browse/OFBIZ-6437
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Affects Versions: Bootstrap theme
>Reporter: Pierre Smits
> Labels: drop-down, menu
>
> Currently when a menu has the same name as a menu item in the applications
> main (appbar) menu and it has TabBar in its name, it is automatically
> regarded as a dropdown menu.
> See: menu-item in app of catalog:
> {code}
> target="ListShipmentMethodTypes"/>
> {code}
> and the menu:
> {code}
> extends-resource="component://common/widget/CommonMenus.xml">
> title="${uiLabelMap.ProductShipmentMethodTypes}">
>
>
> title="${uiLabelMap.ProductQuantityBreaks}">
>
>
> title="${uiLabelMap.ProductCarrierShipmentMethods}">
>
>
>
> {code}
> This shouldn't be the default behaviour. Drop-down menus should be associated
> explicitly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (OFBIZ-6467) Disentangle themes
[ https://issues.apache.org/jira/browse/OFBIZ-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6467. -- Resolution: Not A Problem This has been abandonned it seems > Disentangle themes > -- > > Key: OFBIZ-6467 > URL: https://issues.apache.org/jira/browse/OFBIZ-6467 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Bootstrap theme >Reporter: Pierre Smits > > Currently in the branch the two bootstrap styles (Basic and yellow 'Sunrise) > are entwined. The effect is that when changes are implemented in one theme > they alter the user experience in the other theme. > It would be better to disentangle the 2 styles into separate themes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8250) SvnInfo.ftl and GitInfo.ftl are not generated by default
[ https://issues.apache.org/jira/browse/OFBIZ-8250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502792#comment-15502792 ] Jacopo Cappellato commented on OFBIZ-8250: -- Thank you [~mbrohl] for providing the fix for this annoying error; it was bothering me so thanks for taking the time to implement the patch! > SvnInfo.ftl and GitInfo.ftl are not generated by default > > > Key: OFBIZ-8250 > URL: https://issues.apache.org/jira/browse/OFBIZ-8250 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Fix For: Upcoming Branch > > Attachments: Image 014.png, OFBIZ-8250-2.patch, OFBIZ-8250.patch > > > The two files are not generated which results in an FTL stacktrace in the > footer of the backend applications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6467) Disentangle themes
[ https://issues.apache.org/jira/browse/OFBIZ-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502774#comment-15502774 ] Pierre Smits commented on OFBIZ-6467: - The moment has passed. Both themes didn't end up in the trunk branch. So, why bother? And who cares? > Disentangle themes > -- > > Key: OFBIZ-6467 > URL: https://issues.apache.org/jira/browse/OFBIZ-6467 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Bootstrap theme >Reporter: Pierre Smits > > Currently in the branch the two bootstrap styles (Basic and yellow 'Sunrise) > are entwined. The effect is that when changes are implemented in one theme > they alter the user experience in the other theme. > It would be better to disentangle the 2 styles into separate themes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8292) Use ignore_missing option of the <#include Freemarker directive when fixed
[ https://issues.apache.org/jira/browse/OFBIZ-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502712#comment-15502712 ] Pierre Smits commented on OFBIZ-8292: - The discussion on how many and which theme(s) should be disentangled is not to be done in this issue. > Use ignore_missing option of the <#include Freemarker directive when fixed > -- > > Key: OFBIZ-8292 > URL: https://issues.apache.org/jira/browse/OFBIZ-8292 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > > Working on OFBIZ-8250 and after Deepak at OFBIZ-7942 (too bad I missed that > :/) I found that the ignore_missing option of the <#include Freemarker > directive does not work. I reported to the Freemarker incubating project. > Hopefully this will be fixed. It will then remove the need of creating empty > files for the svn and git info footers when building. > In the meantime I'll provide the change in the themes footers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8223) Broken page renders while click on Submit button on Qualification Screen
[ https://issues.apache.org/jira/browse/OFBIZ-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502620#comment-15502620 ] Avnindra Sharma commented on OFBIZ-8223: Hey [~mbrohl] I have intentionally removed the submit button. There is no use of it and in the result of find screen, there is only on button required i.e delete, which already exists. For more ref: https://ofbiz-vm.apache.org:8443/humanres/control/FindPartyQuals > Broken page renders while click on Submit button on Qualification Screen > > > Key: OFBIZ-8223 > URL: https://issues.apache.org/jira/browse/OFBIZ-8223 > Project: OFBiz > Issue Type: Bug > Components: party >Reporter: Avnindra Sharma >Assignee: Michael Brohl >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-8223.patch > > > Steps to reproduce: > 1. Go to party manager. > 2. Find party Company and navigate to Qualification tab. > 3. Now if there is no existing application and Submit button visible then > click on submit button. > 4. Broken page renders with error message " > :ERROR MESSAGE: > org.ofbiz.webapp.event.EventHandlerException: No rows to process" > Ideally system should hide submit button if there is no application to > process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-8292) Use ignore_missing option of the <#include Freemarker directive when fixed
[ https://issues.apache.org/jira/browse/OFBIZ-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502596#comment-15502596 ] Pierre Smits edited comment on OFBIZ-8292 at 9/19/16 7:36 AM: -- I don't believe that a dependency from one theme on another optional is such a good idea. was (Author: pfm.smits): I don't believe that a dependency from one theme on another is such a good idea. > Use ignore_missing option of the <#include Freemarker directive when fixed > -- > > Key: OFBIZ-8292 > URL: https://issues.apache.org/jira/browse/OFBIZ-8292 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > > Working on OFBIZ-8250 and after Deepak at OFBIZ-7942 (too bad I missed that > :/) I found that the ignore_missing option of the <#include Freemarker > directive does not work. I reported to the Freemarker incubating project. > Hopefully this will be fixed. It will then remove the need of creating empty > files for the svn and git info footers when building. > In the meantime I'll provide the change in the themes footers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8292) Use ignore_missing option of the <#include Freemarker directive when fixed
[ https://issues.apache.org/jira/browse/OFBIZ-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502596#comment-15502596 ] Pierre Smits commented on OFBIZ-8292: - I don't believe that a dependency from one theme on another is such a good idea. > Use ignore_missing option of the <#include Freemarker directive when fixed > -- > > Key: OFBIZ-8292 > URL: https://issues.apache.org/jira/browse/OFBIZ-8292 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > > Working on OFBIZ-8250 and after Deepak at OFBIZ-7942 (too bad I missed that > :/) I found that the ignore_missing option of the <#include Freemarker > directive does not work. I reported to the Freemarker incubating project. > Hopefully this will be fixed. It will then remove the need of creating empty > files for the svn and git info footers when building. > In the meantime I'll provide the change in the themes footers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8292) Use ignore_missing option of the <#include Freemarker directive when fixed
[ https://issues.apache.org/jira/browse/OFBIZ-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-8292: --- Description: Working on OFBIZ-8250 and after Deepak at OFBIZ-7942 (too bad I missed that :/) I found that the ignore_missing option of the <#include Freemarker directive does not work. I reported to the Freemarker incubating project. Hopefully this will be fixed. It will then remove the need of creating empty files for the svn and git info footers when building. In the meantime I'll provide the change in the themes footers. was: Working on OFBIZ-8250 and after Deepak at OFBIZ-7942 (too bad I missed that :/) I found that the ignore_missing option of the <#include Freemarker directive does not work. I reported to the Freemarker incubating project. Hopefully this will be fixed. It will then remove the need ot creating empty files for the svn and git info footers when builiding. In the meantime I'll provide the change in the themes footers. > Use ignore_missing option of the <#include Freemarker directive when fixed > -- > > Key: OFBIZ-8292 > URL: https://issues.apache.org/jira/browse/OFBIZ-8292 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > > Working on OFBIZ-8250 and after Deepak at OFBIZ-7942 (too bad I missed that > :/) I found that the ignore_missing option of the <#include Freemarker > directive does not work. I reported to the Freemarker incubating project. > Hopefully this will be fixed. It will then remove the need of creating empty > files for the svn and git info footers when building. > In the meantime I'll provide the change in the themes footers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8290) Disentangle unused Accounting labels
[ https://issues.apache.org/jira/browse/OFBIZ-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502542#comment-15502542 ] Jacques Le Roux commented on OFBIZ-8290: I add a depends upon link to OFBIZ-8154 to not forget to chime in here when it will be done > Disentangle unused Accounting labels > > > Key: OFBIZ-8290 > URL: https://issues.apache.org/jira/browse/OFBIZ-8290 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: labels, refactoring > Attachments: OFBIZ-8290-AccountingUiLabels.xml.patch > > > Disentanglement of unused labels from the accounting component makes the > component better. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8278) Accounting: Align column titles in list forms
[ https://issues.apache.org/jira/browse/OFBIZ-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranay Pandey reassigned OFBIZ-8278: Assignee: Pranay Pandey (was: Aditi Patidar) > Accounting: Align column titles in list forms > - > > Key: OFBIZ-8278 > URL: https://issues.apache.org/jira/browse/OFBIZ-8278 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Aditi Patidar >Assignee: Pranay Pandey >Priority: Minor > Attachments: OFBIZ-8278.patch, > fixed-asset-std-cost-list-improved.png, fixed-asset-std-cost-list.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8250) SvnInfo.ftl and GitInfo.ftl are not generated by default
[ https://issues.apache.org/jira/browse/OFBIZ-8250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502479#comment-15502479 ] Taher Alkhateeb commented on OFBIZ-8250: Hi Jacques, thank you for the commit. I think it would be more appropriate in the future to let committers commit their own work. Michael added the patch in this JIRA for feedback and help, not committing, as he is the assignee of this JIRA. > SvnInfo.ftl and GitInfo.ftl are not generated by default > > > Key: OFBIZ-8250 > URL: https://issues.apache.org/jira/browse/OFBIZ-8250 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Fix For: Upcoming Branch > > Attachments: Image 014.png, OFBIZ-8250-2.patch, OFBIZ-8250.patch > > > The two files are not generated which results in an FTL stacktrace in the > footer of the backend applications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7650) OFBIZ-7649: Display From date with default now() on all screens under Catalog Application
[ https://issues.apache.org/jira/browse/OFBIZ-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah closed OFBIZ-7650. --- Tested and found them working as expected > OFBIZ-7649: Display From date with default now() on all screens under Catalog > Application > - > > Key: OFBIZ-7650 > URL: https://issues.apache.org/jira/browse/OFBIZ-7650 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: 14.12.01, 15.12.01 >Reporter: Swapnil Shah >Assignee: Swapnil Shah >Priority: Minor > Attachments: OFBIZ-7650.patch > > > To begin with can start fixing it under : > # "Add Product Price" form on > https://ofbiz-vm.apache.org:18443/catalog/control/EditProductPrices?productId=SV-1000 > # "Add Product Category" form on > https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCategories?productId=SV-1000 > # "Add Product Cost Component Calc" form on > https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCosts?productId=SV-1000 > # "Add Content to Product" form on > https://ofbiz-vm.apache.org:18443/catalog/control/EditProductContent?productId=GZ-1000 > Let's keep on adding other screens where it could be fixed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7543) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Order' component
[ https://issues.apache.org/jira/browse/OFBIZ-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Kathawala updated OFBIZ-7543: -- Attachment: OFBIZ-7543-return.patch Added missing patch for Find Return Screen. > OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for > 'Order' component > --- > > Key: OFBIZ-7543 > URL: https://issues.apache.org/jira/browse/OFBIZ-7543 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Upcoming Branch >Reporter: Swapnil Shah >Assignee: Mohammad Kathawala > Attachments: OFBIZ-7543-return.patch, OFBIZ-7543.patch > > > Please refer the details provided on OFBIZ-7542 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7386) Allow user to select multiple options in "Open Order Items" report from basic search criterias while generating report
[ https://issues.apache.org/jira/browse/OFBIZ-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah closed OFBIZ-7386. --- Tested the fixes and found them working fine. > Allow user to select multiple options in "Open Order Items" report from basic > search criterias while generating report > -- > > Key: OFBIZ-7386 > URL: https://issues.apache.org/jira/browse/OFBIZ-7386 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Upcoming Branch >Reporter: Swapnil Shah >Assignee: Swapnil Shah > Attachments: OFBIZ-7386.patch, OrderItemReport.png > > > Currently system allow user to select any specific search criteria link and > hence 'Open Order Items' report is generated only based on any one given > selected criteria. > We can add the feature for generating single report based on multiple values > (possibly via checkbox?) within basic search criteria in this report namely: > 1) Product Store > 2) Order Type (could make it either or selection i.e. either SO or PO with > help of radio button) > 2) Order Status (Here just allow to list only "Created"/"Approved"/"Hold" > order (as systemically only these status should have open item) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8250) SvnInfo.ftl and GitInfo.ftl are not generated by default
[ https://issues.apache.org/jira/browse/OFBIZ-8250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502439#comment-15502439 ] Jacques Le Roux commented on OFBIZ-8250: After reading at http://freemarker.org/docs/ref_directive_include.html the ignore_missing description of this <#include attribute bq. ignore_missing: When true, suppresses the error when the template to include is missing, instead <#include ...> will print nothing. When false, the template processing will stop with error if the template is missing. If you omit this option, then it defaults to false. I thought that we could get rid of the empty files creation when building. But like Deepak [here|https://issues.apache.org/jira/browse/OFBIZ-7942?focusedCommentId=15409322=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15409322 ] I found that it's not working. So I agree that the proposed patch is the best solution so far. I have reopened OFBIZ-7942 because I did not understood the problem there when I closed. We need to report to Apache Freemarker (incubating) because as mentionned Deepak the ignore_missing attribute of the <#include directive does not work. When it will work we will use it and remove the need of creating empty files when running the build task. I commit the proposed patch now, thanks for your patience :) > SvnInfo.ftl and GitInfo.ftl are not generated by default > > > Key: OFBIZ-8250 > URL: https://issues.apache.org/jira/browse/OFBIZ-8250 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Fix For: Upcoming Branch > > Attachments: Image 014.png, OFBIZ-8250-2.patch, OFBIZ-8250.patch > > > The two files are not generated which results in an FTL stacktrace in the > footer of the backend applications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (OFBIZ-7942) GitInfo.ftl cannot be created when sources checkout using svn
[
https://issues.apache.org/jira/browse/OFBIZ-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reopened OFBIZ-7942:
This is like OFBIZ-8250 where a temporary solution is proposed. We need to
report to Apache Freemarker (incubating) because as mentionned Deepak below the
ignore_missing attribute of the <#include directive does not work. When it will
work we will use it and remove the need of creating empty files when running
the build task.
> GitInfo.ftl cannot be created when sources checkout using svn
> -
>
> Key: OFBIZ-7942
> URL: https://issues.apache.org/jira/browse/OFBIZ-7942
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Wai
>Assignee: Jacques Le Roux
> Fix For: Upcoming Branch
>
> Attachments: mycomponent.tar.bz2
>
>
> When running a hot-deploy component and exception occurs. I have included the
> component for reference purposes.
> Used the following steps to create the component...
> -ran $ gradlew createComponent -PcomponentName=mycomponent
> -PcomponentResourceName=myrscname -PwebappName=mywebapp -PbasePermission=NONE
> -added request and associated screen.
> -ran $ gradlew cleanAll loadDefault
> -ran $ gradlew ofbiz
> The console shows the following exception...
> {code}
> FreeMarker template error: Template inclusion failed (for parameter value
> "ofbizhome://runtime/SvnInfo.ftl"):
> /home/wt/wt-mystuff/eclipse/workspace/ofbiz-trunk-test/runtime/SvnInfo.ftl
> (No such file or directory) FTL stack trace ("~" means nesting-related):
> - Failed at: #include "ofbizhome://runtime/SvnInfo... [in template
> "component://tomahawk/template/Footer.ftl" at line 26, column 104] Java
> stack trace (for programmers): freemarker.core._MiscTemplateException:
> [... Exception message was already printed; see it above ...] at
> freemarker.core.Include.accept(Include.java:164) at
> freemarker.core.Environment.visit(Environment.java:326) at
> freemarker.core.Environment.visit(Environment.java:332) at
> freemarker.core.Environment.process(Environment.java:305) at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.renderTemplate(FreeMarkerWorker.java:261)
> at
> org.apache.ofbiz.widget.model.HtmlWidget.renderHtmlTemplate(HtmlWidget.java:167)
> at
> org.apache.ofbiz.widget.model.HtmlWidget$HtmlTemplate.renderWidgetString(HtmlWidget.java:216)
> at
> org.apache.ofbiz.widget.model.HtmlWidget.renderWidgetString(HtmlWidget.java:140)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$PlatformSpecific.renderWidgetString(ModelScreenWidget.java:1321)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:280)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:280)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:280)
> at
> org.apache.ofbiz.widget.model.ModelScreen.renderScreenString(ModelScreen.java:164)
> at
> org.apache.ofbiz.widget.model.ScreenFactory.renderReferencedScreen(ScreenFactory.java:214)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$IncludeScreen.renderWidgetString(ModelScreenWidget.java:780)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
> at
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (OFBIZ-7550) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Project' component
[ https://issues.apache.org/jira/browse/OFBIZ-7550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah closed OFBIZ-7550. --- Tested the fixes and found them working fine. > OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for > 'Project' component > - > > Key: OFBIZ-7550 > URL: https://issues.apache.org/jira/browse/OFBIZ-7550 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/projectmgr >Affects Versions: Trunk >Reporter: Swapnil Shah >Assignee: Swapnil Shah > Attachments: OFBIZ-7550.patch > > > Please refer to details shared over OFBIZ-7542 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7549) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'HR' component
[ https://issues.apache.org/jira/browse/OFBIZ-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah closed OFBIZ-7549. --- Tested the fixes and found them working fine. > OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for > 'HR' component > > > Key: OFBIZ-7549 > URL: https://issues.apache.org/jira/browse/OFBIZ-7549 > Project: OFBiz > Issue Type: Sub-task > Components: humanres >Affects Versions: Trunk >Reporter: Swapnil Shah >Assignee: Swapnil Shah > Attachments: OFBIZ-7549.patch > > > Please refer to details shared over OFBIZ-7542 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7548) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'WorkEffort' component
[ https://issues.apache.org/jira/browse/OFBIZ-7548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah closed OFBIZ-7548. --- Tested the fixes and found them working fine. > OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for > 'WorkEffort' component > > > Key: OFBIZ-7548 > URL: https://issues.apache.org/jira/browse/OFBIZ-7548 > Project: OFBiz > Issue Type: Sub-task > Components: workeffort >Affects Versions: Trunk >Reporter: Swapnil Shah >Assignee: Swapnil Shah > Attachments: OFBIZ-7548.patch > > > Please refer to details shared over OFBIZ-7542 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7546) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Accounting' component
[ https://issues.apache.org/jira/browse/OFBIZ-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah closed OFBIZ-7546. --- Tested the fixes and found them working fine. > OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for > 'Accounting' component > > > Key: OFBIZ-7546 > URL: https://issues.apache.org/jira/browse/OFBIZ-7546 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Swapnil Shah >Assignee: Swapnil Shah > Attachments: OFBIZ-7546.patch > > > Please refer to details shared over OFBIZ-7542 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7545) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Facility' component
[ https://issues.apache.org/jira/browse/OFBIZ-7545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah closed OFBIZ-7545. --- Tested the fixes and found them working fine > OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for > 'Facility' component > -- > > Key: OFBIZ-7545 > URL: https://issues.apache.org/jira/browse/OFBIZ-7545 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Swapnil Shah >Assignee: Swapnil Shah > Attachments: OFBIZ-7545.patch > > > Please refer to details shared over OFBIZ-7542 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
