Release Notes - BloomReach Experience - Open Source CMS

This article covers a Hippo CMS version 12. There's an updated version available that covers our most recent release.

11-11-2018

Release Notes

Compatibility

Plugin Version Bloomreach Experience Manager Release Version
2.6.x 12.6.x
2.5.x 12.5.x
2.4.x 12.4.x
2.3.x 12.3.x
2.2.x 12.2.x
2.1.x 12.1.x
2.0.x 12.0.x
1.x 11.x

Release Notes of 2.6.x

2.6.1

  • Improvement

    • [CRISP-62] - Add response header/body data holder to ExchangeHint
    • [CRISP-64] - [Backport to v12] Let ResourceCacheResolvable to generate cache key
    • [CRISP-67] - Add ExchangeHint#noCache boolean property to let caller cache controllability

2.6.0

  • Improvement

    • [CRISP-53] - Able to configure resource resolvers in spring assembly XML
    • [CRISP-54] - Able to configure a different repository configuration node path
    • [CRISP-58] - [Backport 2.x] Option to not register broker through HippoServiceRegistry

Release Notes of 2.5.x

2.5.0

  • Bug

    • [CRISP-51] - [Backport 12.5] Unable to extract JSON array with scalar elements from Resource object

Release Notes of 2.4.x

2.4.1

  • Task

    • [CRISP-52] - Update CRISP demo to use latest release version

Release Notes of 2.3.x

2.3.2

  • Task

    • [CRISP-52] - Update CRISP demo to use latest release version

2.3.0

  • Improvement

    • [CRISP-45] - Handling unsupported HttpMethods in provided ResourceResolvers
    • [CRISP-47] - Update dependencies for BRE 12.3

Release Notes of 2.2.x

2.2.1

  • Improvement

    • [CRISP-46] - [Backport 12.2] Handling unsupported HttpMethods in provided ResourceResolvers
    • [CRISP-48] - Update dependencies for BRE 12.2

2.2.0

  • Task

    • Branching for BRE 12.2

Release Notes of 2.1.x

2.1.2

  • Bug

    • [CRISP-36] - When a Spring's HttpEntity is passed through ExchangeHint from cms webapp, the HttpEntity cannot be recognized by CRISP core due to classloader issue
  • Improvement

    • [CRISP-35] - Add Hystrix integration example in the demo project

2.1.1

  • New Feature

    • [CRISP-29] - POJO mapping support for JSON based Resources
    • [CRISP-32] - POJO mapping support for XML based Resources
    • [CRISP-33] - Resource Collection POJO mapping support

2.1.0

  • Bug

    • [CRISP-18] - NPE when using CRISP broker service when invoked from custom CMS plugin module
  • New Feature

    • [CRISP-12] - Resolving Binary Data (neither JSON nor XML)
    • [CRISP-23] - Support POST method in resolving/finding resources/binaries
    • [CRISP-30] - Upgrade Jackson Library to 2.8.x
  • Task

    • [CRISP-17] - Move modules in default profile out of profiles
  • Improvement

    • [CRISP-7] - 'Bearer' in Authorization header value to be case-sensitive option
    • [CRISP-21] - RepositoryMapResourceResolverProvider#ResourceResolversInitializingThread prints stack traces unnecessarily on startup

 

Release Notes of 2.0.x

2.0.6

  • Bug

    • [CRISP-37] - [Backport 2.0.x] When a Spring's HttpEntity is passed through ExchangeHint from cms webapp, the HttpEntity cannot be recognized by CRISP core due to classloader issue

2.0.5

  • New Feature

    • [CRISP-24] - [Backport for v12.0] Support POST method in resolving/finding resources/binaries

2.0.4

  • Bug

    • [CRISP-19] - [Backport for v12.0] NPE when using CRISP broker service when invoked from custom CMS plugin module
  • Improvement

    • [CRISP-22] - [Backport for v12.0] RepositoryMapResourceResolverProvider#ResourceResolversInitializingThread prints stack traces unnecessarily on startup

2.0.3

  • New Feature

    • [CRISP-14] - [Backport for v12.0] Resolving Binary Data (neither JSON nor XML)

2.0.2

  • Improvement

    • [CRISP-8] - [Backport for v12.0] 'Bearer' in Authorization header value to be case-sensitive

2.0.1

  • Bug

    • [CRISP-2] - Upgrade External Document Picker in demo
    • [CRISP-4] - When Caching is not enable in ResourceResolver level, ResourceServiceBroker should not cache the resource
    • [CRISP-5] - CRISP 2.0.0 tag contains 2.0.0-SNAPSHOT versions in demo/ folder
  • Improvement

    • [CRISP-3] - Cache resource result in request level by default

2.0.0

  • Initial release for Bloomreach Experience Manager v12 compatibility.
  • Changing the namespace URI of CRISP JSP Tag Libraries to http://www.onehippo.org/jsp/hippo/crisp/tags (from http://www.onehippo.com/jsp/hippo/crisp/tags).
  • Removing 'multiple' for crisp:resourceresolver child nodes to avoid unexpected same name sibling nodes.

 

Release Notes of 1.x and pre-1.x

1.0.4

  • Bug

    • [CRISP-38] - [Backport 1.x] When a Spring's HttpEntity is passed through ExchangeHint from cms webapp, the HttpEntity cannot be recognized by CRISP core due to classloader issue

1.0.3

  • New Feature

    • [CRISP-26] - [Backport for v11] Support POST method in resolving/finding resources/binaries
  • Improvement

    • [CRISP-25] - [Backport for v11] RepositoryMapResourceResolverProvider#ResourceResolversInitializingThread prints stack traces unnecessarily on startup

1.0.2

  • New Feature

    • [CRISP-13] - [Backport for v11] Resolving Binary Data (neither JSON nor XML)

1.0.1

  • Improvement

    • [CRISP-9] - [Backport for v11] 'Bearer' in Authorization header value to be case-sensitive

1.0.0

  • Changing the namespace URI of CRISP JSP Tag Libraries to http://www.onehippo.org/jsp/hippo/crisp/tags (from http://www.onehippo.com/jsp/hippo/crisp/tags).
  • Removing 'multiple' for crisp:resourceresolver child nodes to avoid unexpected same name sibling nodes.

0.9.5

  • Fixing typo in Resource#getResourceType().

0.9.4

  • Correcting groupId, namespace, package names and license headers to be compliant with community projects. e.g, From com.onehippo.cms7.crisp.** to org.onehippo.cms7.crisp.**.

0.9.3

  • JdomResourceResolver addition for XML based REST APIs.

0.9.2

  • Let it throw ResourceException when a resource space is not found.
  • Marketo REST API integration example in demo project.

0.9.1

  • Deploy demo project source packaging zip artifact onto Hippo Maven 2 Enterprise Repository.

0.9.0

  • Initial release.
Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?