[
https://issues.apache.org/jira/browse/JCRVLT-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274479#comment-16274479
]
Tobias Bocanegra commented on JCRVLT-231:
-----------------------------------------
With the repository init feature of sling-start, we can define certain initial
content that will be available in the repository before the first package is
installed. for example in AEM we create {{/libs/granite}} or {{/libs/cq}}.
Packages that depend on this nodes have no way to reference any dependency
package that provides this nodes.
If we would create a "real" package that creates those nodes, we can't install
it in the repository, because it would void the repository init structure. but
filevault would complain, if the package was listed as dependency but not
installed in the repository :-)
so therefor we thought having such an indicator package that helps satisfy the
structural dependencies would be enough.
> Clarify repositoryStructurePackages parameter
> ---------------------------------------------
>
> Key: JCRVLT-231
> URL: https://issues.apache.org/jira/browse/JCRVLT-231
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: package maven plugin
> Affects Versions: package-maven-plugin-1.0.0
> Reporter: Konrad Windszus
>
> Currently the {{repositoryStructurePackages}} parameter is only used in the
> DependencyValidator (to check for collisions and coverage of intermediate
> nodes). But the according packages don't end up in the package's dependencies
> metadata section, therefore this information cannot be evaluated when the
> package is installed somewhere.
> I am wondering why the repositoryStructurePackages should be treated
> differently than any other regular dependency. In any case the javadoc of
> that parameter should be clarified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
