* ERP5Type.PropertySheet becomes a dynamic module that returns strings
  instead of classes for compatibility:
  - the document classes can now use strings in property_sheets attribute
  - if a document uses a string instead of a class reference to point to a
    property sheet, it means that the property sheet can either be an old
    (filesytem, local, in a product) property sheet, or a zodb propertysheet

  For now, the contents of ERP5Type.PropertySheet (strings) are overwritten
  if a local PropertySheet is loaded from the disk. But with time, as
  property sheets will migrate to ZODB, the module will empty itself and
  contain only strings.

* Move all property sheets from all products to ERP5PropertySheetLegacy
  product. Only property sheets that were left 'as is' are CMF* property
  sheets.

This commit is mostly a move to another Product, and should have small
consequences on tests/existing instances.

However, if you used to import PropertySheets in custom/project code
in your custom Property Sheets, you will need to rename:
   from Products.*.PropertySheet.Foo import Foo
to:
   from Products.ERP5PropertySheetLegacy.Foo import Foo



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

 - add check, that well transformation is chosen for resource, removed start date existence - it is tested on order, and acquisition do not works for chcker (???)

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

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

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

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

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

Because there are problems with PropertyExistence, define both
message_property_not_set and message_no_such_property. (see this thread
http://mail.nexedi.com/pipermail/erp5-dev/2008-May/001900.html )


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

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

generation will fail



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

source, source_section, destination and destination_section in 4 constraints to
have better messages.


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

Orders. Currently not enabled by default, as removing constraints is not
really convenient.


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

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

on Payroll Services


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

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

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

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