1. 07 Dec, 2019 8 commits
  2. 06 Dec, 2019 1 commit
    • Nicolas Malin's avatar
      Fixed: Fix missing else during previous refactoring · 071a7423
      Nicolas Malin authored
      When you rendering for with auto-field-entity on edit mode, indicator field has been override by text field.
      Fix also two error on source field type set to FieldInfo.SOURCE_AUTO_SERVICE instead of FieldInfo.SOURCE_AUTO_ENTITY
      Thanks to Olivier Heintz to inform on the regression.
  3. 01 Dec, 2019 7 commits
  4. 30 Nov, 2019 1 commit
  5. 29 Nov, 2019 1 commit
  6. 28 Nov, 2019 6 commits
  7. 27 Nov, 2019 7 commits
  8. 25 Nov, 2019 6 commits
    • Mathieu Lirzin's avatar
      Improved: Do not exclude files from component ‘config’ directories (OFBIZ-11161) · 1a8860a3
      Mathieu Lirzin authored
      With the goal of distributing OFBiz as a library in a Jar, we must
      include every configuration resource files in the Jar.
    • Mathieu Lirzin's avatar
      Improved: Use ‘depends-on’ attribute instead of “component-load.xml” (OFBIZ-11296) · eeabe698
      Mathieu Lirzin authored
      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.
    • Samuel Trégouët's avatar
      Fixed: Remove dependency management from ‘ComponentContainer’ · 00032520
      Samuel Trégouët authored
      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.
    • Jacques Le Roux's avatar
      Fixed: Number problem cancelling order item · 3d555f57
      Jacques Le Roux authored
      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
    • Nicolas Malin's avatar
    • Pawan Verma's avatar
      Fixed: liniting issues introduced by commit d00208ca · fc1e1b48
      Pawan Verma authored
      Thanks: Mathieu Lirzin for report
  9. 23 Nov, 2019 3 commits
    • Mathieu Lirzin's avatar
    • Pawan Verma's avatar
      Fixed: Production run not created for marketing package auto type product if... · d00208ca
      Pawan Verma authored
      Fixed: Production run not created for marketing package auto type product if component inventory is not available
      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.
    • Pawan Verma's avatar
      Fixed: Error while CSR creates a return · 463648a6
      Pawan Verma authored
      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.