[
https://issues.apache.org/jira/browse/JCRVLT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923825#comment-16923825
]
Tobias Bocanegra commented on JCRVLT-220:
-----------------------------------------
it is used to specify the type of content covered by that filter. ideally, a
package should consist of one type. if the `content-package-type` is missing in
the manifest, it is autodetected based on the filter roots. if a filter root is
of type `cleanup` it is ignored for the type detection.
(admittedly, this was a very specific addition to help 'moving' code in
application packages from `/etc/` to `/libs`. hence the name 'cleanup')
> Include package type when assembling a package
> ----------------------------------------------
>
> Key: JCRVLT-220
> URL: https://issues.apache.org/jira/browse/JCRVLT-220
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 3.1.40
> Reporter: Tobias Bocanegra
> Priority: Major
> Fix For: 3.1.42
>
>
> Currently the package page can only be defined with external tools, but not
> when assembling a package.
> it should be possible to:
> - specify the package type during build time
> - have a automatic detection of the package type, based on content or filter.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
