Add support for "oak" XML-Namespace

Description

The XML-Namespaces used to build a content-package are hard-coded in XmlNamespace.java.

Currently the oak namespace is not supported. Therefor it's not possible to create a content-package to define an oak:index definition.

Activity

Show:
Alexander Muthmann
February 25, 2017, 9:02 PM
Edited

Due to the changes in XmlNamespaces I had to increase the version from 1.1.x to 1.2.0

https://github.com/wcm-io/wcm-io-tooling/pull/8

Stefan Seifert
February 28, 2017, 2:52 AM

(please do not set issues with unmerged PRs to resolved)

the list of default list of namespaces is hardcoded, but the API of the content package builder allows to add your own ones. i assume you you are using this in context of CONGA, and in CONGA it's not yet possible to define additional XML namespaces for generated packages.

nevertheless it makes sense to add the oak NS to the list of default namespaces.

Alexander Muthmann
February 28, 2017, 2:54 AM

Sry, didn't know the workflow

Yes, the issue happens from conga

Stefan Seifert
February 28, 2017, 2:57 AM

PR is merged

Fixed

Assignee

Unassigned

Reporter

Alexander Muthmann

Labels

None

Components

Fix versions

Priority

Major