|Guide - 7.8 API Changes||7.8|
|Guide - 7.8 Content Model Changes||7.8|
|Guide - 7.8 Migration Addresses||7.7|
|Guide - 7.8 Migration B2B Selection of a Cost Center to an order||7.8|
|Guide - 7.8 Migration Branding Package||7.8|
|Guide - 7.8 Migration Enhanced Content Sharing||7.8|
|Guide - 7.8 Migration Hints||7.8|
|Guide - 7.8 Migration Preference Definitions for Subscriptions||7.7|
|Guide - 7.8 Migration Removal of bc_product_configuration||7.8|
|Guide - 7.8 Migration Secure Cookie Settings||7.8|
|Guide - 7.8 Migration URL Rewrite Handler|
|Guide - 7.8.3 Build and Deployment||7.8|
This also means that the following versions of the a_responsive multiproject are using Gradle Tools 2.11.6 and the assemblies are now located in the multiproject.
Furthermore the Version Recommender Plugin is used instead of the old versioning plugin and the source packages of the assemblies inspired-b2c and inspired-b2x are not longer separate files of a hotfix or patch delivery for the starter store.
If you start a new project based on the above mentioned versions, please stick to the the documentation for the setup of a Continuous Integration environment as described in the Cookbook - Setup CI Infrastructure.
Intershop strongly recommends to update the Gradle Tools and all used plugins to the latest suggested versions even for existing projects. The dependencies and versions are included in the build script in the root of the multi-project a_responsive. The migration steps are described in the section Migrate Tools Version of the Public Release Notes - Gradle Tools - Version 2.11.
Be aware that these changes significantly improve further development, simplify maintenance and reduce future testing efforts.
To consume changes via hotfix or patch releases of a_responsive without any changes on the build configuration, it is necessary to ignore the assembly projects ('inspired_b2*') and the build configuration in the root of a_responsive. Depending on the used "versioning plugin" it is necessary to change the version of Intershop Commerce Management in the gradle.properties file or in the .ivyIcm-b2?.version to consume the latest version of Intershop Commerce Management.
In the most cases it is not necessary to take over changes from the correct assembly - b2c / b2x - build file, but if so it is necessary to merge the changes from the build file to the own assembly build file manually.
Since 7.8, the preparer execution order is calculated based on the version number only. For more details refer to Cookbook - DBMigrate.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.