Follow nexedi/erp5@1664e541

It seems developpers didn't update their instances.

Creating a Software Publication doesn't require to change the Software Product.

And so, simplify the code logic, as product is always created before the publication

Do not wait too long when pushing a new application.

Do not modify document history if nothing changed

Set the wildcard URL on a system preference.

Those web site do not work in offline mode, so client must revalidate the components.

Update appcache

Drop unused scripts

Thanks to Vincent Bechu for his work on this commit.

As noted in a comment in this BT's Base_redirect implementation, original code
does raise when abort_transaction is true.
Not raising in this implementation means that this script will return to caller,
while it never does on original code.
Also, to add insult to injury, this utterly bogus implementation interferes with
transaction boundaries. So suddenly, a single publication spans over 2
transactions, which can lead to:
- ZODB Connection sharing, breaking transaction isolation
- the second transaction implicitly created by this abort (actually, by the next
transactional connector registration to transaction) may be committed,
in which case anything done after Base_redirect returns will be
persistently committed, against caller's explicitly specified intent, and against
all developer expectations.

NEVER TOUCH TRANSACTION ! Only CMFActivity and unittests are allowed
this level of access (and CMFActivity should be modified out of this exceptional
state).

Linshare Use the same configuration than ERP5

Thanks to Vincent Bechu for his work on this topic.

This reverts commit fba5767e.

Sorry, I went too quickly, there was difference between self and context

This reverts commit 7aa5fb76

> this change makes title empty when reply
nexedi/erp5!823 (comment 73439)

/reviewed-on nexedi/erp5!826

only calculate exchange rate if necessary
use transaction cache
make getExchangeRate as local function

remove useless test_21
update test_20 with various packing list

multiple owner test case
multiple cancel packing list test
circular movement test