Fork me on GitHub

Compatibility

Plugin version Bloomreach XM Release version
7.x 16.x
6.x 15.x
5.x 14.x
4.x 13.x
3.x 12.x
2.x 11.x, 10.x
1.x 7.9.x

Release Notes

7.0.0

Release Date: 15 Aug 2024

  • FORGE-528 - Upgrade for XM 16, JDK 17 compatibility.

6.0.0

Release Date: 23 Aug 2022

5.0.0

Release Date: 12 May 2021

  • HIPFORGE-405 - Upgrade for XM 14 compatibility.
  • The artifacts' groupId was changed from org.onehippo.forge.doc-commenting to org.bloomreach.forge.doc-commenting (but no repackaging of Java classes though).
  • Added bootstrapping of domain /hippo:configuration/hippo:domains/doccommenting to the plugin, instead of doing this in an implementing project. Please check the upgrade path: best approach is to first remove this node from project yamls, then redo any changes.

4.0.0

Release Date: 19 January 2019

Release Notes (3.x)

Release Date: 1 October 2018

3.0.1

  • HIPFORGE-200 -Categorize doccommentdata's child nodes as system.

3.0.0

  • Compliant with Hippo CMS 12.

Release Notes (2.x)

2.1.7

  • Do not update comment item if there's no real change when user clicks on OK button in the dialog.

2.1.6

  • Clone CommentItem object in the editor dialog, not to cache the old one after cancellation.

2.1.5

  • Pass CommentingContext in DefaultJcrCommentPersistenceManager#mapCommentNode() and #bindCommentNode() for more extensibility.

2.1.4

  • Always set doccommenting:lastModified properly even when created first time.

2.1.3

  • Configuring security domain for /doccommentdata in demo project and update the site documentation.
  • Bootstrapping /doccommentdata node during initialization.

2.1.2

  • Initial release

Release Notes (1.x)

1.1.7

  • Do not update comment item if there's no real change when user clicks on OK button in the dialog.

1.1.6

  • Clone CommentItem object in the editor dialog, not to cache the old one after cancellation.

1.1.5

  • Pass CommentingContext in DefaultJcrCommentPersistenceManager#mapCommentNode() and #bindCommentNode() for more extensibility.

1.1.4

  • Always set doccommenting:lastModified properly even when created first time.

1.1.3

  • Configuring security domain for /doccommentdata in demo project and update the site documentation.
  • Bootstrapping /doccommentdata node during initialization.

1.1.2

  • Initial release