[
https://issues.apache.org/jira/browse/JCRVLT-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684536#comment-16684536
]
Tobias Bocanegra commented on JCRVLT-279:
-----------------------------------------
there are opinions to this:
a) the lazy approach is indeed to include the {{.content.xml}} of the ancestor
nodes. this is what the exporter does by default. the importer respects those
definitions when it needs to create a non existing parent. this approach is
mostly used in AEM before we had clearly defined dependencies. it might cause
problems, if the ancestor node definitions differ from package to package.
b) the satisfied dependencies and repository-structure approach. AEM 6.4 we
started to enforce that all parent nodes of the filter roots need to be present
in the repository before the package is installed. this is enforced through
dependencies. to initial, toplevel, nodes are created during repository init
and "exported" as reference through the repository-structure package.
> Emit warning/error in case embedded file/subpackage is overwritten by
> jcrRootSourceDirectory
> --------------------------------------------------------------------------------------------
>
> Key: JCRVLT-279
> URL: https://issues.apache.org/jira/browse/JCRVLT-279
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
> Affects Versions: package-maven-plugin-1.0.1
> Reporter: Konrad Windszus
> Priority: Minor
> Fix For: package-maven-plugin-1.0.4
>
>
> Due to errorneous project setup it may sometimes happen that the
> {{jcrRootSourceDirectory}} inadvertently contains the to be embedded file.
> Since the {{jcrRootSourceDirectory}} is having a higher precedence all files
> in there overwrite previously embedded files. In that case a warning/error
> should be emitted. The same for sub packages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
