Split Discussion Thread reference generator into a separate testable method. Be more strict in generated reference.

Conflicts:

	bt5/erp5_discussion/bt/revision

ref. http://comments.gmane.org/gmane.comp.web.zope.cvs/22117

Instead use brain's type to determine type of value rather than examine
first returned catalog row (contributed by Vincent).

first row from catalog (espc. when multiple security uids case which
are not always filled in - i.e. mostly default None)

Revert b2fc99d7 (default security is expected to work without changing table structure)

way it's exported / imported and tested.

a new bt5 (erp5_security_uid_innodb_catalog) upon installation.
Add all generic ZSQL methods to this new bt5
so projects can adjust only the minimum required.

need to change catalog as this can be quite time consuming.

Adjust tests as local roles structure changed.

Revert "clean up reportPaymentStatus function on PaypalService to call PaypalService_reportPaymentStatus script regardless of the outcome of the status and added one test to cover this method"

This reverts commit 03e358bc.

One test was failing

Avoid to catalog some special roles like Owner (defined in getSQLCatalog().getSQLCatalogRoleKeysList()).
As __ac_local_roles_group_id_dict__ changed its structure to 'local_group_id': ['Role'] (just the opposite)
adjust test as well.

clean up reportPaymentStatus function on PaypalService to call PaypalService_reportPaymentStatus script regardless of the outcome of the status and added one test to cover this method

not pollute with more than required rows table roles_and_users.
As result this will increase a bit object database.

remove paramater that is not supported on IPaymentService and refactor code to be possible pass a list of parameters to page template. With this will be possible create one form more ergonomic to post to paypal

Forgot to bump egg version.

This is ERP5SecurePayment service which aims to provide paypal integration following ERP5SecurePayment interface.

Revert 97d2dbbb (we do not need to generate all entries per feed request only the most recent once as client code is expected to keep a "local" copy instead).

Revert 17045076 (we do not need to generate all entries per feed request only the most recent once as client code is expected to keep a "local" copy instead).

use the interpreter's import lock instead of threading.RLock in ERP5Type.dynamic to avoid possible dead lock.

Try to support migration of old instances (containing old erp5_property_sheets)
with recent products. This is especially visible with BusinessTemplate property sheet
when new filesystem versions require an up to date erp5_property_sheets bt5 which itself
can not be installed.

Make sure the failure in testLegacyDeliveryBuilderToSupportMultipleLines.TestNestedLine.test_04_MergingMultipleSaleOrders happens always.

It was random because of the order of executed activities.