[
https://issues.apache.org/jira/browse/JCRVLT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073164#comment-16073164
]
Tobias Bocanegra edited comment on JCRVLT-188 at 7/4/17 6:10 AM:
-----------------------------------------------------------------
but for checking the installed state, you need the {{lastUnpacked}} property.
see the test:
https://github.com/tripodsan/jackrabbit-filevault/blob/7dc540be7b72a7f4a034f1279ffe2aa2812ed47f/vault-core/src/test/java/org/apache/jackrabbit/vault/packaging/integration/TestArchiveExtraction.java#L97
was (Author: tripod):
but for checking the installed state, you need the {{lastUnpackaged}} property.
see the test:
https://github.com/tripodsan/jackrabbit-filevault/blob/7dc540be7b72a7f4a034f1279ffe2aa2812ed47f/vault-core/src/test/java/org/apache/jackrabbit/vault/packaging/integration/TestArchiveExtraction.java#L97
> Allow to figure out the created date for hollow packages
> --------------------------------------------------------
>
> Key: JCRVLT-188
> URL: https://issues.apache.org/jira/browse/JCRVLT-188
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 3.1.40
> Reporter: Konrad Windszus
>
> Currently for hollow packages (JCRVLT-50) only the following meta information
> is stored in the repository:
> * name
> * version
> * group
> * lastUnpacked
> * lastUnpackedBy
> * lastModified
> * lastModifiedBy
> What is missing is a {{jcr:created}} date which would allow to check if a
> to-be extracted hollow package has already been extracted previously in the
> repository.
> I am interested to prevent duplicate installations of the same hollow
> packages in the system and only the {{jcr:created}} would allow to achieve
> that (compare with JCRVLT-155).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
