You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2016/12/21 06:13:58 UTC

[jira] [Commented] (JCRVLT-32) Store package properties in the MANIFEST.MF for faster access

    [ https://issues.apache.org/jira/browse/JCRVLT-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766247#comment-15766247 ] 

Tobias Bocanegra commented on JCRVLT-32:
----------------------------------------

suggest to add/use the following manifest property names:

{noformat}
Jackrabbit-Vault-PackageId: ...
Jackrabbit-Vault-Dependencies: ...
Jackrabbit-Vault-Description: ...
{noformat}

The other properties like {{acHandling}}, {{requiresRoot}} are only required for actual installation and can reside in the {{properties.xml}}


> Store package properties in the MANIFEST.MF for faster access
> -------------------------------------------------------------
>
>                 Key: JCRVLT-32
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-32
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>            Priority: Minor
>
> this is somewhat related to JCRVLT-31. 
> With the current implementation, one must read the entire package in order to figure out the package properties. If they would be store in a MANIFEST.MF, which has to be the first entry in a .jar, we can use a resettable inputstream to read the properties. this allows to quickly get the important information of a package, such as package id and dependencies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)