[
https://issues.apache.org/jira/browse/JCRVLT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073211#comment-16073211
]
Konrad Windszus commented on JCRVLT-188:
----------------------------------------
{{lastUnpacked}} does not help here as this only contains the unpacked date.
That does no allow to derive the information whether the same (!!) package has
already been installed. I want to derive from the package id and its creation
date whether exactly this version has been installed already (before I
extract/upload the new package). Since there is no hash in the metadata, the
creation date is enough to uniquely identify a package (the PID is not enough
unfortunately if you think about SNAPSHOT versions). The unpack date does not
help here, just think about a package with id
{{mygroup:package:0.0.1-SNAPSHOT}}. Only by comparing the creation date I could
determine whether this package is worth to be extracted/uploaded again.
> 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)
