Entando Plugin: Content Versioning

Manages the versioning of portal content, storing the history of performed operations

License

License

GroupId

GroupId

org.entando.entando.plugins
ArtifactId

ArtifactId

entando-plugin-jpversioning
Last Version

Last Version

6.2.6
Release Date

Release Date

Type

Type

war
Description

Description

Entando Plugin: Content Versioning
Manages the versioning of portal content, storing the history of performed operations
Project URL

Project URL

https://central.entando.com/entando-plugin-jpversioning
Project Organization

Project Organization

Entando Inc.

Download entando-plugin-jpversioning

How to add to project

<!-- https://jarcasting.com/artifacts/org.entando.entando.plugins/entando-plugin-jpversioning/ -->
<dependency>
    <groupId>org.entando.entando.plugins</groupId>
    <artifactId>entando-plugin-jpversioning</artifactId>
    <version>6.2.6</version>
    <type>war</type>
</dependency>
// https://jarcasting.com/artifacts/org.entando.entando.plugins/entando-plugin-jpversioning/
implementation 'org.entando.entando.plugins:entando-plugin-jpversioning:6.2.6'
// https://jarcasting.com/artifacts/org.entando.entando.plugins/entando-plugin-jpversioning/
implementation ("org.entando.entando.plugins:entando-plugin-jpversioning:6.2.6")
'org.entando.entando.plugins:entando-plugin-jpversioning:war:6.2.6'
<dependency org="org.entando.entando.plugins" name="entando-plugin-jpversioning" rev="6.2.6">
  <artifact name="entando-plugin-jpversioning" type="war" />
</dependency>
@Grapes(
@Grab(group='org.entando.entando.plugins', module='entando-plugin-jpversioning', version='6.2.6')
)
libraryDependencies += "org.entando.entando.plugins" % "entando-plugin-jpversioning" % "6.2.6"
[org.entando.entando.plugins/entando-plugin-jpversioning "6.2.6"]

Dependencies

compile (2)

Group / Artifact Type Version
org.entando.entando.plugins : entando-plugin-jacms jar 6.2.17
org.entando.entando : entando-portal-ui jar 6.2.6

provided (2)

Group / Artifact Type Version
javax.servlet : javax.servlet-api jar 3.1.0
javax.servlet.jsp : jsp-api jar 2.2

test (12)

Group / Artifact Type Version
org.entando.entando : entando-engine test-jar 6.2.23
org.entando.entando : entando-admin-console test-jar 6.2.36
org.entando.entando : entando-portal-ui test-jar 6.2.6
org.entando.entando.plugins : entando-plugin-jacms test-jar 6.2.17
org.springframework : spring-test jar 5.1.8.RELEASE
junit : junit jar 4.12
org.mockito : mockito-core jar 2.28.2
org.assertj : assertj-core jar 3.11.1
org.hamcrest : hamcrest-all jar 1.3
com.jayway.jsonpath : json-path-assert jar 2.2.0
org.apache.derby : derbyclient jar 10.9.1.0
org.apache.derby : derby jar 10.9.1.0

Project Modules

There are no modules declared in this project.

Build Status Quality Gate Status Coverage Vulnerabilities Code Smells Security Rating Technical Debt

entando-plugin-jpversioning

Versioning

Code: jpversioning

Description

The Versioning Plugin allows to trace, and restore selectively, the versions of single contents. This plugin adds new administration interfaces related to the content tracking; the resources - here intended as attachments and images – receive a slightly different treatment: changes across the same element are not traced, instead a backup of all the deleted resources is kept. Please also be aware that a resource referenced by older versions of the content cannot be deleted to avoid inconsistency on restore. Though the plugin installation is not difficult at all, we are going to modify the system tables, so a backup of your database is highly recommended. Furthermore, you may be required to customize the scripts to your needs before installation.

Installation

In order to install the Versioning Plugin, you must insert the following dependency in the pom.xml file of your project:

<dependency>
    <groupId>org.entando.entando.plugins</groupId>
    <artifactId>entando-plugin-jpversioning</artifactId>
    <version>${entando.version}</version>
    <type>war</type>
</dependency>

Configuration

You can access to Versioning Plugin’s functionality through the usual left menu: Plugins -> Versioning in the Administration Area. Selecting Contents from the Plugins menu, you can access to the Contents history management.

Clicking on the content description you can access to the history of the selected content. For each content we are given the possibility to manage various version by clicking on the description as well as some information, such as the date of the modification the user which made the changes.

Regarding the version number's rule, the content version is characterized from the pattern <major_number>.<minor_number>, a new version of the content always increases the minor number. The major number is incremented (and the minor number is set to zero) only when a content is published.

You can also restore the content to the wanted version by clicking the arrow icon, or delete the record (version numbers don't change in this case).

Please note that the restore action when confirmed, loads only a previous version of the content. You have to save your changes with the Save button to finalize the restore process. Naturally the version replaced is tracked by the plugin.

Regarding Resource (Attachments and Images) are traced only when deleted. That is, if you edit a resource and change the file or the description your changes are not saved.

Resources are placed in a recycle bin so that they can be later restored only when deleted. The recycle bin can be access from the left menu PluginsVersioningImages or Attachments. You can restore and delete permanently the resources using the arrow and the remove icons.

Developing against local versions of upstream projects (e.g. admin-console, entando-engine).

Full instructions on how to develop against local versions of upstream projects are available in the entando-parent-bom project.

org.entando.entando.plugins

Entando Inc

Open source micro frontend platform for Kubernetes.

Versions

Version
6.2.6
6.1.1
6.1.0
5.3.2
5.3.1
5.2.0
5.1.0
5.0.3
5.0.2
5.0.1
5.0.0
4.3.2
4.3.1
4.2.0-TP1
4.0.0
3.2.0
3.0.0