[jira] [Updated] (JCRVLT-188) Allow to figure out the created date for hollow packages

2017-06-30 Thread Konrad Windszus (JIRA)

 [ 
https://issues.apache.org/jira/browse/JCRVLT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated JCRVLT-188:
---
Description: 
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).

  was:
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 does already exist in the system. 
I am interested to prevent duplicate installations of the same hollow packages 
in the system and only the {{jcr:created}} would allow that (compare with 
JCRVLT-155).


> 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)


[jira] [Updated] (JCRVLT-188) Allow to figure out the created date for hollow packages

2017-06-30 Thread Konrad Windszus (JIRA)

 [ 
https://issues.apache.org/jira/browse/JCRVLT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated JCRVLT-188:
---
Summary: Allow to figure out the created date for hollow packages  (was: 
Allow to figure out on which created date a hollow package is based on)

> 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 does already exist in the system. 
> I am interested to prevent duplicate installations of the same hollow 
> packages in the system and only the {{jcr:created}} would allow that (compare 
> with JCRVLT-155).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)