[
https://issues.apache.org/jira/browse/JCRVLT-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra updated JCRVLT-170:
------------------------------------
Description:
For code deployment scenarios the simplicity of filter roots and the accuracy
of dependencies is more important than for normal content packages.
also the mixture of content/code and ACL might be problematic.
for application packages the following rules should apply:
- they expose a specific manifest header: {{Content-Package-Type: application}}
- the workspace filter must not contain regexps and no import modes
- it should not contain content (i.e. nodes outside /apps, /libs, ...)
- it should not mix code and ACLs
- it must define dependencies to packages that define the parent nodes of all
filters
- (other type of packages are {{content}}, {{mixed}}, {{container}}
was:
For code deployment scenarios the simplicity of filter roots and the accuracy
of dependencies is more important than for normal content packages.
also the mixture of content/code and ACL might be problematic.
for application packages the following rules should apply:
- they expose a specific manifest header: {{Jackrabbit-Vault-Package-Type: app}}
- the workspace filter must not contain regexps and no import modes
- it should not contain content (i.e. nodes outside /apps, /libs, ...)
- it should not mix code and ACLs
- it must define dependencies to packages that define the parent nodes of all
filters
> Introduce the concept of application (code) packages
> ----------------------------------------------------
>
> Key: JCRVLT-170
> URL: https://issues.apache.org/jira/browse/JCRVLT-170
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Reporter: Tobias Bocanegra
>
> For code deployment scenarios the simplicity of filter roots and the accuracy
> of dependencies is more important than for normal content packages.
> also the mixture of content/code and ACL might be problematic.
> for application packages the following rules should apply:
> - they expose a specific manifest header: {{Content-Package-Type:
> application}}
> - the workspace filter must not contain regexps and no import modes
> - it should not contain content (i.e. nodes outside /apps, /libs, ...)
> - it should not mix code and ACLs
> - it must define dependencies to packages that define the parent nodes of all
> filters
> - (other type of packages are {{content}}, {{mixed}}, {{container}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
