Tobias Bocanegra created JCRVLT-229:
---------------------------------------
Summary: add support for forcing re-registration of nodetypes
Key: JCRVLT-229
URL: https://issues.apache.org/jira/browse/JCRVLT-229
Project: Jackrabbit FileVault
Issue Type: Improvement
Components: Packaging
Affects Versions: 3.1.42
Reporter: Tobias Bocanegra
The current nodetype import handling does not re-register nodetypes if they
already exist in the repository. the reason why vault doesn't update the
nodetype is that it might not always be desired. since every package
automatically includes all the nodetypes it uses, installing it in an "older"
repository might downgrade the nodetypes and cause a lot of problems.
for specific "upgrade-packages" it might be necessary to force a
re-registration of the nodetype. I suggest to either to allow the nodetypes in
the CND to be annotated to force update, eg:
{noformat}
@ForceRegister
[sling:Folder] > nt:folder
- * (undefined) multiple
- * (undefined)
+ * (nt:base) = sling:Folder version
{noformat}
but then we need to tweak the CND parser...or preprocess the cnd.
alternatively, the information could be added to the package properties, eg:
{noformat}
reregisterNodeTypes="sling:Folder"
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
