[
https://issues.apache.org/jira/browse/JCRVLT-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680588#comment-16680588
]
Tobias Bocanegra commented on JCRVLT-279:
-----------------------------------------
hmm...in general, the package importer starts importing the content based on
the filter roots. usually, the order doesn't matter, since the filters should
specify disjunct sets. due to the non-atomic nature of the package extractor,
it might be that observation listeners start processing content before related
content is available. for example in the bug mentioned in the code:
{quote}
When creating the package via maven tooling the order of the resources is using
the "natural" filesystem order. In this specific case the "/content/dam" will
appear before "/etc/tags"
While installing the generated package on a fresh AEM (automation in jenkins),
the tags get removed from the asset as the tags are not yet existing , and a
service implemented by
"https://git.corp.adobe.com/CQ/platform/blob/master/bundles/cq-tagging/src/main/java/com/day/cq/tagging/impl/JcrTagManagerImpl.java";
will wipe non existing tags from the asset.
{quote}
However, meanwhile I think relying on the order of the entries is wrong. the
proper fix for that problem would have been to create 2 packages for tags and
assets, and the make the assets one depend on tags.
> 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
>
> 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)
