[jira] [Closed] (OFBIZ-10546) Notifications Mailing List is missing on OFBiz website
[ https://issues.apache.org/jira/browse/OFBIZ-10546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane closed OFBIZ-10546. -- Resolution: Implemented > Notifications Mailing List is missing on OFBiz website > -- > > Key: OFBIZ-10546 > URL: https://issues.apache.org/jira/browse/OFBIZ-10546 > Project: OFBiz > Issue Type: Improvement > Components: site >Reporter: Swapnil M Mane >Assignee: Swapnil M Mane >Priority: Minor > Attachments: Notification_Mailing_List.png, > Notification_Mailing_List_2X2.png, OFBIZ-10546.patch, OFBIZ-10546_2X2.patch > > > We created notifications list in past to migrate the traffic of Jira > notifications from dev list to notifications list. > The information about this mailing list is missing on OFBiz website. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10546) Notifications Mailing List is missing on OFBiz website
[ https://issues.apache.org/jira/browse/OFBIZ-10546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607904#comment-16607904 ] Swapnil M Mane commented on OFBIZ-10546: Thanks [~jacques.le.roux], [~deepak.dixit] and [~suraj.khurana] This change have been committed at rev#1840337. > Notifications Mailing List is missing on OFBiz website > -- > > Key: OFBIZ-10546 > URL: https://issues.apache.org/jira/browse/OFBIZ-10546 > Project: OFBiz > Issue Type: Improvement > Components: site >Reporter: Swapnil M Mane >Assignee: Swapnil M Mane >Priority: Minor > Attachments: Notification_Mailing_List.png, > Notification_Mailing_List_2X2.png, OFBIZ-10546.patch, OFBIZ-10546_2X2.patch > > > We created notifications list in past to migrate the traffic of Jira > notifications from dev list to notifications list. > The information about this mailing list is missing on OFBiz website. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7113) Refactoring permission model call
[ https://issues.apache.org/jira/browse/OFBIZ-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin updated OFBIZ-7113: - Attachment: OFBIZ-7113.patch > Refactoring permission model call > - > > Key: OFBIZ-7113 > URL: https://issues.apache.org/jira/browse/OFBIZ-7113 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Minor > Attachments: OFBIZ-7113.patch, OFBIZ-7113.patch, OFBIZ-7113.patch > > > With the subject on mailing list "Permission service not on the same > transaction" : http://markmail.org/message/34vxi4ntmbj7vzcr > I started the improvement but the java code need to be clean and refactoring. > I share my first draft patch, but need more works. I realize : > * unified call evalPermission > * move all related field for permission service on ModelService to > ModelPermission > * Remove deprecated code > * start labelized error message > * add new attributes on permission model : required-new-transaction and > return-error-on-failure -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-7113) Refactoring permission model call
[ https://issues.apache.org/jira/browse/OFBIZ-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607354#comment-16607354 ] Nicolas Malin commented on OFBIZ-7113: -- Ohhh, effectively the commit 1818708 break this patch, I regenerate it after rebasing it on trunk. I also saw that I forgot to load my tests on the previous patch :) Now with this [^OFBIZ-7113.patch]it's ok ! > Refactoring permission model call > - > > Key: OFBIZ-7113 > URL: https://issues.apache.org/jira/browse/OFBIZ-7113 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Minor > Attachments: OFBIZ-7113.patch, OFBIZ-7113.patch, OFBIZ-7113.patch > > > With the subject on mailing list "Permission service not on the same > transaction" : http://markmail.org/message/34vxi4ntmbj7vzcr > I started the improvement but the java code need to be clean and refactoring. > I share my first draft patch, but need more works. I realize : > * unified call evalPermission > * move all related field for permission service on ModelService to > ModelPermission > * Remove deprecated code > * start labelized error message > * add new attributes on permission model : required-new-transaction and > return-error-on-failure -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10515) Impersonation of userLogin feature
[ https://issues.apache.org/jira/browse/OFBIZ-10515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607178#comment-16607178 ] Gil Portenseigne commented on OFBIZ-10515: -- This new patch provide more configuration controls (in security.properties), and control to not allow ADMIN or more Privilege users. This add also a config that prevent the impersonated user to make any action during impersonation with a nice screen, that refresh itself every 30 seconds, and offer a way to logout for the user. > Impersonation of userLogin feature > -- > > Key: OFBIZ-10515 > URL: https://issues.apache.org/jira/browse/OFBIZ-10515 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Minor > Fix For: Upcoming Branch > > Attachments: ImpersonationWidget.png, OFBIZ-10515.patch, > OFBIZ-10515.patch, impersonate-ico.png, impersonateButton.png > > > This JIRA introduce a new feature that allow the impersonation of a login by > an authorized user. > This is implemeted with :· > * A new service ‘userImpersonate’ that will check security, store > impersonation in UserLoginHistory, and return the new session > * Events ‘userImpersonate’ and ‘userDepersonate’ that will allow > impersonation/depersonation action persisting current user session > * A new modal widget in the common-theme that inform the user about > ‘impersonation in process’ and offering a way to depersonate. > * A new field in UserLoginHistory to store impersonation originator > * A button in party viewprofile page to illustrate the feature -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10553) Convert QuoteServices.xml mini lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-10553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Ouvrard updated OFBIZ-10553: Attachment: OFBIZ-10553.patch > Convert QuoteServices.xml mini lang to groovy > - > > Key: OFBIZ-10553 > URL: https://issues.apache.org/jira/browse/OFBIZ-10553 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Antoine Ouvrard >Priority: Minor > Attachments: OFBIZ-10553.patch > > > This is an attempt to migrate QuoteServices.xml to groovy file version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10553) Convert QuoteServices.xml mini lang to groovy
Antoine Ouvrard created OFBIZ-10553: --- Summary: Convert QuoteServices.xml mini lang to groovy Key: OFBIZ-10553 URL: https://issues.apache.org/jira/browse/OFBIZ-10553 Project: OFBiz Issue Type: Sub-task Components: order Affects Versions: Trunk Reporter: Antoine Ouvrard This is an attempt to migrate QuoteServices.xml to groovy file version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10540) Warning in console logs related to entity definitions
[ https://issues.apache.org/jira/browse/OFBIZ-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin closed OFBIZ-10540. - Resolution: Fixed Fix Version/s: Upcoming Branch Ok I commited the corrective patch on trunk at 1840296 Thanks Deepak(s) :) > Warning in console logs related to entity definitions > - > > Key: OFBIZ-10540 > URL: https://issues.apache.org/jira/browse/OFBIZ-10540 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Nicolas Malin >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10540.patch, OFBIZ-10540.patch, OFBiz-10540.patch, > OFBiz-10540.patch > > > On trunk, following warnings related to entity definitions are coming: > 2018-08-27 14:10:32,129 |delegator-startup-1 |GenericDelegator |W| =-=-=-=-= > Found 5 warnings when checking the entity definitions: > 2018-08-27 14:10:32,130 |delegator-startup-1 |GenericDelegator |W| > [RelationRelatedFieldNotFound] The field "partyId" of related entity > FacilityContactMech was specified in the keymaps but is not found for > relation FacilityContactMech of entity FacilityAndContactMech. > 2018-08-27 14:10:32,131 |delegator-startup-1 |GenericDelegator |W| > [RelationFieldNotFound] The field partyId was specified in the keymaps but is > not found for relation FacilityContactMech of entity FacilityAndContactMech. > 2018-08-27 14:10:32,131 |delegator-startup-1 |GenericDelegator |W| > [RelationRelatedFieldNotFound] The field "contactMechPurposeTypeId" of > related entity WorkEffortContactMech was specified in the keymaps but is not > found for relation WorkEffortContactMech of entity WorkEffortAndContactMech. > 2018-08-27 14:10:32,131 |delegator-startup-1 |GenericDelegator |W| > [RelationFieldNotFound] The field contactMechPurposeTypeId was specified in > the keymaps but is not found for relation WorkEffortContactMech of entity > WorkEffortAndContactMech. > 2018-08-27 14:10:32,131 |delegator-startup-1 |GenericDelegator |W| > [RelationFieldNotFound] The field contactMechPurposeTypeId was specified in > the keymaps but is not found for relation ContactMechPurposeType of entity > WorkEffortAndContactMech. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10515) Impersonation of userLogin feature
[ https://issues.apache.org/jira/browse/OFBIZ-10515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-10515: - Attachment: OFBIZ-10515.patch > Impersonation of userLogin feature > -- > > Key: OFBIZ-10515 > URL: https://issues.apache.org/jira/browse/OFBIZ-10515 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Minor > Fix For: Upcoming Branch > > Attachments: ImpersonationWidget.png, OFBIZ-10515.patch, > OFBIZ-10515.patch, impersonate-ico.png, impersonateButton.png > > > This JIRA introduce a new feature that allow the impersonation of a login by > an authorized user. > This is implemeted with :· > * A new service ‘userImpersonate’ that will check security, store > impersonation in UserLoginHistory, and return the new session > * Events ‘userImpersonate’ and ‘userDepersonate’ that will allow > impersonation/depersonation action persisting current user session > * A new modal widget in the common-theme that inform the user about > ‘impersonation in process’ and offering a way to depersonate. > * A new field in UserLoginHistory to store impersonation originator > * A button in party viewprofile page to illustrate the feature -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16606953#comment-16606953 ] Deepak Nigam commented on OFBIZ-10518: -- Attached the initial patch for the proposed 'Supply Allocation Feature' for review and feedback. Will be updating this patch with time for further improvements and additions. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, EditAllocationPlan.png, > FindAllocationPlan.png, OFBiz-10518-Supply-Allocation-Plan.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518-Supply-Allocation-Plan.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, EditAllocationPlan.png, > FindAllocationPlan.png, OFBiz-10518-Supply-Allocation-Plan.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10552) Move Acccounint AP AR webapps to plugin
[ https://issues.apache.org/jira/browse/OFBIZ-10552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin updated OFBIZ-10552: -- Description: As exchanged on [this discussion |https://lists.apache.org/thread.html/111ad6488cf6d1888004dca149d70f4131844fab3ac1215d7b236aa3@%3Cdev.ofbiz.apache.org%3E]I created the first patch [^OFBIZ-10552.patch] that contains the separation between accounting component and AP/AR webapps. I detected cross dependency on screens between accounting and AP /AR, so I realized following change : * the commissionRun link in accounting to keep this present on AP * move all Financial account deposit payment group screen from AR to Accounting You can see the svn status command result [^OFBIZ-10552-status.txt] that will be helpfull to read the patch. To test without plugin ap-ar: * apply patch [^OFBIZ-10552.patch] * ./gradlew ofbiz To test with plugin ap-ar * apply patch [^OFBIZ-10552.patch] * ^untar [^accounting-ap-ar.tar.gz] at the ofbiz home^ * ./gradlew loadAll ofbiz I named the plugin accounting-ap-ar but you'll probably find a much better name :) was: As exchanged on [this discussion |https://lists.apache.org/thread.html/111ad6488cf6d1888004dca149d70f4131844fab3ac1215d7b236aa3@%3Cdev.ofbiz.apache.org%3E]I created the first patch [^OFBIZ-10552.patch] that contains the separation between accounting component and AP/AR webapps. I detected cross dependency on screens between accounting and AP /AR, so I realized following change : * the commissionRun link in accounting to keep this present on AP * move all Financial account deposit payment group screen from AR to Accounting You can see the svn status command result [^OFBIZ-10552-status.txt] that will be helpfull to read the patch. To test without plugin ap-ar: * apply patch [^OFBIZ-10552.patch] * ./gradlew ofbiz To test with plugin ap-ar * apply patch [^OFBIZ-10552.patch] * ^untar [^accounting-ap-ar.tar.gz] at the ofbiz home^ * ./gradlew loadAll ofbiz I named the plugin > Move Acccounint AP AR webapps to plugin > --- > > Key: OFBIZ-10552 > URL: https://issues.apache.org/jira/browse/OFBIZ-10552 > Project: OFBiz > Issue Type: Task > Components: accounting >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Major > Attachments: OFBIZ-10552-status.txt, OFBIZ-10552.patch, > accounting-ap-ar.tar.gz > > > As exchanged on [this discussion > |https://lists.apache.org/thread.html/111ad6488cf6d1888004dca149d70f4131844fab3ac1215d7b236aa3@%3Cdev.ofbiz.apache.org%3E]I > created the first patch [^OFBIZ-10552.patch] that contains the separation > between accounting component and AP/AR webapps. > I detected cross dependency on screens between accounting and AP /AR, so I > realized following change : > * the commissionRun link in accounting to keep this present on AP > * move all Financial account deposit payment group screen from AR to > Accounting > You can see the svn status command result [^OFBIZ-10552-status.txt] that > will be helpfull to read the patch. > To test without plugin ap-ar: > * apply patch [^OFBIZ-10552.patch] > * ./gradlew ofbiz > To test with plugin ap-ar > * apply patch [^OFBIZ-10552.patch] > * ^untar [^accounting-ap-ar.tar.gz] at the ofbiz home^ > * ./gradlew loadAll ofbiz > I named the plugin accounting-ap-ar but you'll probably find a much better > name :) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10552) Move Acccounint AP AR webapps to plugin
[ https://issues.apache.org/jira/browse/OFBIZ-10552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin updated OFBIZ-10552: -- Description: As exchanged on [this discussion |https://lists.apache.org/thread.html/111ad6488cf6d1888004dca149d70f4131844fab3ac1215d7b236aa3@%3Cdev.ofbiz.apache.org%3E]I created the first patch [^OFBIZ-10552.patch] that contains the separation between accounting component and AP/AR webapps. I detected cross dependency on screens between accounting and AP /AR, so I realized following change : * the commissionRun link in accounting to keep this present on AP * move all Financial account deposit payment group screen from AR to Accounting You can see the svn status command result [^OFBIZ-10552-status.txt] that will be helpfull to read the patch. To test without plugin ap-ar: * apply patch [^OFBIZ-10552.patch] * ./gradlew ofbiz To test with plugin ap-ar * apply patch [^OFBIZ-10552.patch] * ^untar [^accounting-ap-ar.tar.gz] at the ofbiz home^ * ./gradlew loadAll ofbiz I named the plugin was: As exchanged on [this discussion |https://lists.apache.org/thread.html/111ad6488cf6d1888004dca149d70f4131844fab3ac1215d7b236aa3@%3Cdev.ofbiz.apache.org%3E]I created the first patch that contains the separation between accounting component and AP/AR webapps. I detected cross dependency on screens between accounting and AP /AR, so I realized following change : * the commissionRun link in accounting to keep this present on AP * move all Financial account deposit payment group screen from AR to Accounting > Move Acccounint AP AR webapps to plugin > --- > > Key: OFBIZ-10552 > URL: https://issues.apache.org/jira/browse/OFBIZ-10552 > Project: OFBiz > Issue Type: Task > Components: accounting >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Major > Attachments: OFBIZ-10552-status.txt, OFBIZ-10552.patch, > accounting-ap-ar.tar.gz > > > As exchanged on [this discussion > |https://lists.apache.org/thread.html/111ad6488cf6d1888004dca149d70f4131844fab3ac1215d7b236aa3@%3Cdev.ofbiz.apache.org%3E]I > created the first patch [^OFBIZ-10552.patch] that contains the separation > between accounting component and AP/AR webapps. > I detected cross dependency on screens between accounting and AP /AR, so I > realized following change : > * the commissionRun link in accounting to keep this present on AP > * move all Financial account deposit payment group screen from AR to > Accounting > You can see the svn status command result [^OFBIZ-10552-status.txt] that > will be helpfull to read the patch. > To test without plugin ap-ar: > * apply patch [^OFBIZ-10552.patch] > * ./gradlew ofbiz > To test with plugin ap-ar > * apply patch [^OFBIZ-10552.patch] > * ^untar [^accounting-ap-ar.tar.gz] at the ofbiz home^ > * ./gradlew loadAll ofbiz > I named the plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10552) Move Acccounint AP AR webapps to plugin
[ https://issues.apache.org/jira/browse/OFBIZ-10552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin updated OFBIZ-10552: -- Attachment: OFBIZ-10552-status.txt OFBIZ-10552.patch > Move Acccounint AP AR webapps to plugin > --- > > Key: OFBIZ-10552 > URL: https://issues.apache.org/jira/browse/OFBIZ-10552 > Project: OFBiz > Issue Type: Task > Components: accounting >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Major > Attachments: OFBIZ-10552-status.txt, OFBIZ-10552.patch, > accounting-ap-ar.tar.gz > > > As exchanged on [this discussion > |https://lists.apache.org/thread.html/111ad6488cf6d1888004dca149d70f4131844fab3ac1215d7b236aa3@%3Cdev.ofbiz.apache.org%3E]I > created the first patch that contains the separation between accounting > component and AP/AR webapps. > I detected cross dependency on screens between accounting and AP /AR, so I > realized following change : > * the commissionRun link in accounting to keep this present on AP > * move all Financial account deposit payment group screen from AR to > Accounting > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10552) Move Acccounint AP AR webapps to plugin
[ https://issues.apache.org/jira/browse/OFBIZ-10552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin updated OFBIZ-10552: -- Attachment: accounting-ap-ar.tar.gz > Move Acccounint AP AR webapps to plugin > --- > > Key: OFBIZ-10552 > URL: https://issues.apache.org/jira/browse/OFBIZ-10552 > Project: OFBiz > Issue Type: Task > Components: accounting >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Major > Attachments: accounting-ap-ar.tar.gz > > > As exchanged on [this discussion > |https://lists.apache.org/thread.html/111ad6488cf6d1888004dca149d70f4131844fab3ac1215d7b236aa3@%3Cdev.ofbiz.apache.org%3E]I > created the first patch that contains the separation between accounting > component and AP/AR webapps. > I detected cross dependency on screens between accounting and AP /AR, so I > realized following change : > * the commissionRun link in accounting to keep this present on AP > * move all Financial account deposit payment group screen from AR to > Accounting > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10552) Move Acccounint AP AR webapps to plugin
Nicolas Malin created OFBIZ-10552: - Summary: Move Acccounint AP AR webapps to plugin Key: OFBIZ-10552 URL: https://issues.apache.org/jira/browse/OFBIZ-10552 Project: OFBiz Issue Type: Task Components: accounting Affects Versions: Trunk Reporter: Nicolas Malin Assignee: Nicolas Malin As exchanged on [this discussion |https://lists.apache.org/thread.html/111ad6488cf6d1888004dca149d70f4131844fab3ac1215d7b236aa3@%3Cdev.ofbiz.apache.org%3E]I created the first patch that contains the separation between accounting component and AP/AR webapps. I detected cross dependency on screens between accounting and AP /AR, so I realized following change : * the commissionRun link in accounting to keep this present on AP * move all Financial account deposit payment group screen from AR to Accounting -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-499) Implement ShoppingCartEvents and CheckoutEvents as simple-mehtods
[ https://issues.apache.org/jira/browse/OFBIZ-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16606858#comment-16606858 ] Gil Portenseigne commented on OFBIZ-499: [~pfm.smits] agree that we should close ! > Implement ShoppingCartEvents and CheckoutEvents as simple-mehtods > - > > Key: OFBIZ-499 > URL: https://issues.apache.org/jira/browse/OFBIZ-499 > Project: OFBiz > Issue Type: Improvement > Components: order >Reporter: Chris Howe >Priority: Minor > Attachments: CompareJavaCodeToMinilang.patch, > CompareJavaCodeToMinilang.patch, Shopping Cart.mm, Shopping Cart.mm, > ShoppingCart.jpeg, ShoppingCartItem.jpeg, ShoppingCartItem.mm > > > Recreate the ShoppingCartEvents and CheckoutEvents as simple methods so they > will be easier to override/play with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9275) Add a Gradle task to svn update all plugins
[
https://issues.apache.org/jira/browse/OFBIZ-9275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16606821#comment-16606821
]
Pierre Smits commented on OFBIZ-9275:
-
Removing 'Fix Version' from Open and Unresolved ticket.
> Add a Gradle task to svn update all plugins
> ---
>
> Key: OFBIZ-9275
> URL: https://issues.apache.org/jira/browse/OFBIZ-9275
> Project: OFBiz
> Issue Type: Improvement
> Components: Gradle
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
>
> When you svn update the framework, unlike for svn:externals, it does not
> update the plugins because it's an embedded working copy. So I have tried
> that w/o success so far:
> {code}
> Index: build.gradle
> ===
> --- build.gradle (revision 1788020)
> +++ build.gradle (working copy)
> @@ -17,6 +17,7 @@
> * under the License.
> */
> import at.bxm.gradleplugins.svntools.tasks.SvnCheckout
> +import at.bxm.gradleplugins.svntools.tasks.SvnUpdate
> import org.apache.tools.ant.filters.ReplaceTokens
> /*
> @@ -774,6 +775,14 @@
> }
> }
> +task updateAllPluginsSource(group: ofbizPlugin,
> +description: 'Update all plugins from source control.') {
> +
> +task updatePluginsFromSvn(type: SvnUpdate) {
> +workspaceDir = "${pluginsDir}"
> +}
> +}
> +
> // == Clean up tasks ==
> task cleanCatalina(group: cleanupGroup, description: 'Clean Catalina data in
> runtime/catalina/work') {
> doLast { delete "${rootDir}/runtime/catalina/work" }
> {code}
> The doc is here
> https://github.com/martoe/gradle-svntools-plugin/blob/master/docs/SvnUpdate.md
> https://github.com/martoe/gradle-svntools-plugin/blob/master/src/main/groovy/at/bxm/gradleplugins/svntools/tasks/SvnUpdate.groovy
> BTW somehow related there is no Gradle svn plugin way to get the status. So
> you have to move to the plugins directory. A bit tedious, I propose a
> pluginsStatus.bat script for that (could be in tools but I'll move it in
> another branch)
> {code}
> @echo off
> cd plugins
> svn st
> cd ..
> {code}
> If we agree I can add the same pluginsStatus.sh
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-9275) Add a Gradle task to svn update all plugins
[
https://issues.apache.org/jira/browse/OFBIZ-9275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-9275:
Fix Version/s: (was: 17.12.01)
> Add a Gradle task to svn update all plugins
> ---
>
> Key: OFBIZ-9275
> URL: https://issues.apache.org/jira/browse/OFBIZ-9275
> Project: OFBiz
> Issue Type: Improvement
> Components: Gradle
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
>
> When you svn update the framework, unlike for svn:externals, it does not
> update the plugins because it's an embedded working copy. So I have tried
> that w/o success so far:
> {code}
> Index: build.gradle
> ===
> --- build.gradle (revision 1788020)
> +++ build.gradle (working copy)
> @@ -17,6 +17,7 @@
> * under the License.
> */
> import at.bxm.gradleplugins.svntools.tasks.SvnCheckout
> +import at.bxm.gradleplugins.svntools.tasks.SvnUpdate
> import org.apache.tools.ant.filters.ReplaceTokens
> /*
> @@ -774,6 +775,14 @@
> }
> }
> +task updateAllPluginsSource(group: ofbizPlugin,
> +description: 'Update all plugins from source control.') {
> +
> +task updatePluginsFromSvn(type: SvnUpdate) {
> +workspaceDir = "${pluginsDir}"
> +}
> +}
> +
> // == Clean up tasks ==
> task cleanCatalina(group: cleanupGroup, description: 'Clean Catalina data in
> runtime/catalina/work') {
> doLast { delete "${rootDir}/runtime/catalina/work" }
> {code}
> The doc is here
> https://github.com/martoe/gradle-svntools-plugin/blob/master/docs/SvnUpdate.md
> https://github.com/martoe/gradle-svntools-plugin/blob/master/src/main/groovy/at/bxm/gradleplugins/svntools/tasks/SvnUpdate.groovy
> BTW somehow related there is no Gradle svn plugin way to get the status. So
> you have to move to the plugins directory. A bit tedious, I propose a
> pluginsStatus.bat script for that (could be in tools but I'll move it in
> another branch)
> {code}
> @echo off
> cd plugins
> svn st
> cd ..
> {code}
> If we agree I can add the same pluginsStatus.sh
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-499) Implement ShoppingCartEvents and CheckoutEvents as simple-mehtods
[ https://issues.apache.org/jira/browse/OFBIZ-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16606820#comment-16606820 ] Pierre Smits commented on OFBIZ-499: Should we not close this ticket as the community decided to move services from simple methods to groovy? > Implement ShoppingCartEvents and CheckoutEvents as simple-mehtods > - > > Key: OFBIZ-499 > URL: https://issues.apache.org/jira/browse/OFBIZ-499 > Project: OFBiz > Issue Type: Improvement > Components: order >Reporter: Chris Howe >Priority: Minor > Attachments: CompareJavaCodeToMinilang.patch, > CompareJavaCodeToMinilang.patch, Shopping Cart.mm, Shopping Cart.mm, > ShoppingCart.jpeg, ShoppingCartItem.jpeg, ShoppingCartItem.mm > > > Recreate the ShoppingCartEvents and CheckoutEvents as simple methods so they > will be easier to override/play with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10551) Remove unused labels from ProductUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-10551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10551: - Attachment: OFBIZ-10551-ProductUiLabels.xml.patch > Remove unused labels from ProductUiLabels.xml > - > > Key: OFBIZ-10551 > URL: https://issues.apache.org/jira/browse/OFBIZ-10551 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-10551-ProductUiLabels.xml.patch > > > Component UI labels get added when code changes are introduced. But it can > also happen that the (unused) label is forgotten while doing code clean-ups, > refactoring of the change before a patch submitted or a commit is executed. > Or that progressing insight leads to have the code change go into a different > component > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10551) Remove unused labels from ProductUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-10551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10551: - Description: Component UI labels get added when code changes are introduced. But it can also happen that the (unused) label is forgotten while doing code clean-ups, refactoring of the change before a patch submitted or a commit is executed. Or that progressing insight leads to have the code change go into a different component was: Component UI labels get added when code changes are introduced. But it can also happen that the label is forgotten while doing code clean-ups, refactoring of the change before a patch submitted or a commit is executed. Or that progressing insight leads to have the code change go into a different component. > Remove unused labels from ProductUiLabels.xml > - > > Key: OFBIZ-10551 > URL: https://issues.apache.org/jira/browse/OFBIZ-10551 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > > Component UI labels get added when code changes are introduced. But it can > also happen that the (unused) label is forgotten while doing code clean-ups, > refactoring of the change before a patch submitted or a commit is executed. > Or that progressing insight leads to have the code change go into a different > component > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10551) Remove unused labels from ProductUiLabels.xml
Pierre Smits created OFBIZ-10551: Summary: Remove unused labels from ProductUiLabels.xml Key: OFBIZ-10551 URL: https://issues.apache.org/jira/browse/OFBIZ-10551 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits Component UI labels get added when code changes are introduced. But it can also happen that the label is forgotten while doing code clean-ups, refactoring of the change before a patch submitted or a commit is executed. Or that progressing insight leads to have the code change go into a different component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
