Componize 3.2.0 (9 Jan 2019)

New features

Fluid Topics integration

A new componize-fluid-topics AMP is now available providing integration with one or more Fluid Topics servers. The integration uses an XProc output processing pipeline to package a DITA Map and all dependencies into a ZIP archive which is then uploaded via a new dedicated XProc step to a Fluid Topics server. For more information see the Fluid Topics section of the Componize Administration Guide.

Technical changes

  • A new custom XProc step (cpnz:fluid-topics) can be used to upload files to a Fluid Topics server.
  • The XML schema language used for validation is now configurable using the componize.xml.schemaLanguage property. By default it is set to http://www.w3.org/XML/XMLSchema/v1.0.
  • The "Map View" (beta) now uses the DITA class attribute and should work with DITA specializations.
  • Rendition URIs are no longer double encoded.
  • A new REST API (/componize/vcs/tag/list?repositoryId={repositoryId}) has been added to retrieve the list of tags for a repository. This improves performance when listing tags in the Branches dashlet.
  • Support for Alfresco Enterprise 5.2.4.

Bug fixes

  • #18742: The source language folder node was locked during import. The translation status metadata has been moved from the source language folder node to a dedicated node in a new /vcs:graphRoot folder at the root of workspace://SpacesStore/. This only applies to newly created source folders.
  • #19322: Creating a tag may cause an out of memory. When creating a tag, the snapshot (ZIP archive) was created in memory before being written to disk. It is now created directly on disk.

Known issues

  • Bug #1350: The DITA Open Toolkit htmlsearch plugin creates a file xx.html in TOMCAT_HOME. The workaround is to make sure the tomcat user has write access to the xx.html file.