Main changes are:
- new amount generator
- new simulation is used by default but legacy simulation is still available
- BT refactoring

New amount generator:
- compatible with linear amount generator lines.
- 'create_line' property is deprecated: a amount is generated only if a resource
  is set.
- non-linear amount generator lines need to be migrated:
  - an empty base_application can't be used anymore to generate a fixed quantity
  - support of 'calculation_script_id' is dropped: it is replaced by a
    type-based Xxx_getBaseAmountQuantityMethod script.
  - 'target_level' property is replaced by 'target_delivery'
  - 'create_line' propret

About new simulation, the most visible changes are:
- movements (or deliveries) must be linked (directly or not) to a configured
  Business Process, otherwise 'expand' fails
- specialise values are propagated through simulation
- erp5_* BT do not provide rules anymore, nor erp5_default_business_process
- deliveries and movements can not contain Trade Model Lines (or any other kind
  of Amount Generator Line) anymore
- rules can't contain "cells" anymore (like in Invoice Transcation Rule):
  this is now configured with Trade Model Paths on the Business Process

BT refactoring:
- 'erp5_simulation' is not experimental anymore: it should contain everything
  related to simulation. It is required even if legacy simulation is used.
- old simulation is provided via BT: it can be used by installing
  'erp5_simulation_legacy' and specific BT like 'erp5_trade_simulation_legacy',
  'erp5_accounting_simulation_legacy', etc.
- 'erp5_simulation_test' BT contains 'erp5_default_business_process' and new
  rules for unit tests

ERP5Legacy is required for legacy simulation, but it can also be installed without any issue if it is unused.

Unit tests:
Tests in ERP5 product test new simulation. Many of those testing simulation are
duplicated in ERP5Legacy in order to be tested with legacy simulation.
Some tests fail with new simulation or need to be rewritten.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39918 20353a03-c40f-0410-a6d1-a30d3c3de9de

document_publication_workflow is too complicated for this simple purpose. publication_workflow should be used instead. If required, publication_workflow will be improved.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39917 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39916 20353a03-c40f-0410-a6d1-a30d3c3de9de

work not to fail in this case expectedFailure is just a way to hide a not
working bt.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39915 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39914 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39913 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39912 20353a03-c40f-0410-a6d1-a30d3c3de9de

   libraries provide its profile


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39911 20353a03-c40f-0410-a6d1-a30d3c3de9de

"""
In the erp5_project BT5:
erp5_project_trade/PurchaseOrder_view[my_title]
-> erp5_project_trade/Base_viewTradeFieldLibrary[my_view_mode_title]
-> erp5_trade/Base_viewTradeFieldLibrary[my_view_mode_title]
"""
So Base_viewTradeFieldLibrary can exists in erp5_project only if it is contained in folder named
erp5_project_trade.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39910 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39909 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39908 20353a03-c40f-0410-a6d1-a30d3c3de9de

 - use rpath to put be sure that dynamic libraries will be loaded from
   proper places (especially important in case of using on non clean
   machine which provide libraries in standard places)


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39907 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39906 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39905 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39904 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39903 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39902 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39901 20353a03-c40f-0410-a6d1-a30d3c3de9de

define a new icon on organisation instead of document_icon.gif. The original I use is available there : http://commons.wikimedia.org/wiki/File:Enterprise_buildings_icons.png and is in public domain.

Reviewed by thierry

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39900 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39899 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39898 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39897 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39896 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39895 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39894 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39893 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39892 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39891 20353a03-c40f-0410-a6d1-a30d3c3de9de

* fix wrong usages of except.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39890 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39889 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39888 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39887 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39886 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39885 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39884 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39883 20353a03-c40f-0410-a6d1-a30d3c3de9de

In base edit, we translate '' to None before passing the kw to edit. This was done only for main fields, but not for listbox/matrixbox editable field. This commit makes the behaviour consistent by applying the same translation to listbox and matrixbox.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39882 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39881 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39880 20353a03-c40f-0410-a6d1-a30d3c3de9de

You can now add and remove interfaces to Portal Types on the fly.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39879 20353a03-c40f-0410-a6d1-a30d3c3de9de