Guide - 7.10 Build and Deployment

1 Build Configuration Changes

1.1 Update Gradle Tools from 2.11.7 to 2.11.8

  • Default configuration of messaging is changed to JGroups 

1.2 Update Gradle Tools from 2.11.8 to 2.11.9

1.3 SCM Version Plugin Update to 2.6.0

  • In case the scm-version plugin is not well configured, the ivy publishing process will now fail with the error Invalid publication 'ivy': revision cannot contain '/'.

Please correct your configuration, depending on your project style guide, e.g. for often used branch pattern:

scm {
    prefixes {
        stabilizationPrefix = 'stabilization'
        featurePrefix = 'feature'
        hotfixPrefix = 'hotfix'
        bugfixPrefix = 'bugfix'
        prefixSeperator = '/'
    }
    ...
}

2 Deployment Configuration Changes

2.1 Moving Cartridge Properties to jar

We moved all cartridge properties (e.g. bc_mail.properties) in to src/main/resources. This means the deployment cannot override or exclude these files anymore. Please validate your deploy.gradle files and remove the according section. It is possible to override configuration depending on your need within your projects (e.g. /staticfiles/cartridge/config/your.properties).

2.2 Moving logback-<cartridge-name>.xml

In case your deployment extensions refer to standard logback configurations, you need to adapt the location

Old LocationNew LocationReleaseHint
bc_pricing/staticfiles/share/system/config/cartridges/logback-bc_pricing.xmlbc_pricing/staticfiles/cartridge/logback/logback-bc_pricing.xml7.10.2.2in release 7.10.1.8 the file was moved to src/main/resources and cannot be adapted
bc_basket_service/staticfiles/share/system/config/cartridges/logback-bc_basket_service.xmlbc_basket_service/staticfiles/cartridge/logback/logback-bc_basket_service.xml7.10.2.2in release 7.10.1.8 the file was moved to src/main/resources and cannot be adapted
bc_contract/staticfiles/share/system/config/cartridges/logback-bc_contract.xmlbc_contract/staticfiles/cartridge/logback/logback-bc_contract.xml7.10.6.1




Disclaimer

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.

Customer Support
Knowledge Base
Product Resources
Support Tickets