ofbiz-framework

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Improved: Use ‘depends-on’ attribute instead of “component-load.xml” (OFBIZ-11296)

We currently have two ways to define component loading order. Either

by using ‘depends-on’ attribute in “component-config.xml” or by adding

a “component-load.xml” file at the root of a component directory.

“depends-on” is more flexible because it handles partial ordering when

“component-load.xml” defines a total order which is not necessarily

meaningful, so it is better to rely only “depends-on”.

This removes the usage of “component-load.xml” to use ‘depends-on’

instead. The dependency declarations correspond to the total ordering

previously defined but will need to be refined in the future to relax

unnecessary dependency declarations.

Only “framework/base/config/component-load.xml” which defines the

top-level directories order (framework, applications, themes and

plugins) is kept.

    • -0
    • +1
    /applications/content/ofbiz-component.xml
    • -0
    • +1
    /applications/order/ofbiz-component.xml
    • -0
    • +1
    /applications/party/ofbiz-component.xml
    • -0
    • +1
    /applications/product/ofbiz-component.xml
    • -0
    • +1
    /framework/catalina/ofbiz-component.xml
  1. … 10 more files in changeset.
Fixed: Remove dependency management from ‘ComponentContainer’ (OFBIZ-11275)

This fixes a bug identified by ‘testCheckDependencyForComponent’ where

the dependencies declared inside component configurations were not

impacting the component retrieval order.

Component configurations stored in the cache can now be properly

sorted based on their <depends-on> declaration. The new

‘ComponentConfig#sortDependencies’ method returns a collection of

component configuration following a topological ordering.

In case of dependency cycle we throw an error.

Fixed: Number problem cancelling order item (OFBIZ-11283)

If an order item has a quantity greater then 1000, cancelling the order item via

the order form in backend does not work.

In the Demo (trunk) environment: the quantity of 1200 to cancel is displayed as

"1,200" in the quantity input field.

--> an error is displayed

On my local installation I use a different locale and it is displayed as "1.200".

--> interprets the dot as a comma and the quantity of 1,2 is cancelled

Create Order: Order Mgt --> Order Entry --> Sales Order (Customer: DemoCustomer)

--> ProductId: GZ-2644, Quantity 1200 --> Finalize order

On order: Edit Items --> click checkbox next to quantity -->cancel selected items

jleroux: I have applied the same in ReceiveInventory.ftl

Thanks: Ingo Wolfmayr for report and test. Ankush Upadhyay for the fix

Fixed: Number problem cancelling order item (OFBIZ-11283)

If an order item has a quantity greater then 1000, cancelling the order item via

the order form in backend does not work.

In the Demo (trunk) environment: the quantity of 1200 to cancel is displayed as

"1,200" in the quantity input field.

--> an error is displayed

On my local installation I use a different locale and it is displayed as "1.200".

--> interprets the dot as a comma and the quantity of 1,2 is cancelled

Create Order: Order Mgt --> Order Entry --> Sales Order (Customer: DemoCustomer)

--> ProductId: GZ-2644, Quantity 1200 --> Finalize order

On order: Edit Items --> click checkbox next to quantity -->cancel selected items

jleroux: I have applied the same in ReceiveInventory.ftl

Thanks: Ingo Wolfmayr for report and test. Ankush Upadhyay for the fix

Fixed: Number problem cancelling order item (OFBIZ-11283)

If an order item has a quantity greater then 1000, cancelling the order item via

the order form in backend does not work.

In the Demo (trunk) environment: the quantity of 1200 to cancel is displayed as

"1,200" in the quantity input field.

--> an error is displayed

On my local installation I use a different locale and it is displayed as "1.200".

--> interprets the dot as a comma and the quantity of 1,2 is cancelled

Create Order: Order Mgt --> Order Entry --> Sales Order (Customer: DemoCustomer)

--> ProductId: GZ-2644, Quantity 1200 --> Finalize order

On order: Edit Items --> click checkbox next to quantity -->cancel selected items

jleroux: I have applied the same in ReceiveInventory.ftl

Thanks: Ingo Wolfmayr for report and test. Ankush Upadhyay for the fix

Fixed: Remove unneeded space after parenthesis

Fixed: liniting issues introduced by commit d00208c (OFBIZ-10585)

Thanks: Mathieu Lirzin for report

Fixed: liniting issues introduced by commit d00208c (OFBIZ-10585)

Thanks: Mathieu Lirzin for report

Fixed: liniting issues introduced by commit d00208c (OFBIZ-10585)

Thanks: Mathieu Lirzin for report

Fixed: Corrected variable name. Nothing functional. (OFBIZ-10585)

Fixed: Production run not created for marketing package auto type product if component inventory is not available (OFBIZ-10585)

When we create an order for marketing package auto, the system checks the component inventory and if found then it creates the production run job and produce marketing package inventory, but if component quantity not available then it does not create the job. So if we don't have an inventory item of component then production run should be created with created status.

Thanks: Yashwant Dhakad for report and Ankush Upadhyay for the patch.

Fixed: Production run not created for marketing package auto type product if component inventory is not available (OFBIZ-10585)

When we create an order for marketing package auto, the system checks the component inventory and if found then it creates the production run job and produce marketing package inventory, but if component quantity not available then it does not create the job. So if we don't have an inventory item of component then production run should be created with created status.

Thanks: Yashwant Dhakad for report and Ankush Upadhyay for the patch.

Fixed: Production run not created for marketing package auto type product if component inventory is not available (OFBIZ-10585)

When we create an order for marketing package auto, the system checks the component inventory and if found then it creates the production run job and produce marketing package inventory, but if component quantity not available then it does not create the job. So if we don't have an inventory item of component then production run should be created with created status.

Thanks: Yashwant Dhakad for report and Ankush Upadhyay for the patch.

Fixed: Error while CSR creates a return (OFBIZ-11068)

Added check to validate Payment Method passed from UI while creating return. If not available in system, throw an error.

Thanks: Dikpal Kanungo for report and Rohit Hukkeri for the patch.

Fixed: Error while CSR creates a return (OFBIZ-11068)

Added check to validate Payment Method passed from UI while creating return. If not available in system, throw an error.

Thanks: Dikpal Kanungo for report and Rohit Hukkeri for the patch.

Fixed: Error while CSR creates a return (OFBIZ-11068)

Added check to validate Payment Method passed from UI while creating return. If not available in system, throw an error.

Thanks: Dikpal Kanungo for report and Rohit Hukkeri for the patch.

Fixed: Usage of 'include-form' instead of 'include-grid' in PartyScreens.xml for grid elements (OFBIZ-11286)

In PartyScreens.xml there were 'ListInvoicesApplPayments', 'ListUnAppliedInvoices' and 'ListUnAppliedPayments' include as form instead of grid but in PartyForms.xml they are defined as grids.

Thanks to Ulrich Heidfeld to raise and solve this issue

Fixed: Usage of 'include-form' instead of 'include-grid' in PartyScreens.xml for grid elements (OFBIZ-11286)

In PartyScreens.xml there were 'ListInvoicesApplPayments', 'ListUnAppliedInvoices' and 'ListUnAppliedPayments' include as form instead of grid but in PartyForms.xml they are defined as grids.

Thanks to Ulrich Heidfeld to raise and solve this issue

Fixed: Usage of 'include-form' instead of 'include-grid' in PartyScreens.xml for grid elements (OFBIZ-11286)

In PartyScreens.xml there were 'ListInvoicesApplPayments', 'ListUnAppliedInvoices' and 'ListUnAppliedPayments' include as form instead of grid but in PartyForms.xml they are defined as grids.

Thanks to Ulrich Heidfeld to raise and solve this issue

Improved: Add enconding type attribute for import data file tools (OFBIZ-10234) During the import of file via datafile import you may want to set encoding type. Actually only the type UTF-8 is supported. This commit allows to add a new "encoding-type" attribute into data-file to indicate the type of encoding of the imported file.

Thanks to Pierre Gaudin for this improvement.

No functional change

Removes new line added to test Buildbot config after INFRA-19443

No functional change

Just a new line added to test Buildbot config after INFRA-19443

No functional change

Removes new line added to test Buildbot config after INFRA-19443

No functional change

Just a new line added to test Buildbot config after INFRA-19443

Improved: Define ‘gradlew’ variable in “build.gradle” only once

Improved: no functional change

Fixes Wrong version name. Actually more to test INFRA-19443

"Trigger OFBiz Buildbot on commits"

Improved: no functional change

Fixes Wrong version name. Actually more to test INFRA-19443

"Trigger OFBiz Buildbot on commits"

Fixed: Add missing view permissions checks to various screens.

    • -0
    • +3
    /applications/humanres/widget/CommonScreens.xml
Fixed: Add missing view permissions checks to various screens.

    • -0
    • +3
    /applications/humanres/widget/CommonScreens.xml
Fixed: Add missing view permissions checks to various screens.

    • -0
    • +3
    /applications/humanres/widget/CommonScreens.xml