[
https://issues.apache.org/jira/browse/JCRVLT-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691746#comment-17691746
]
Konrad Windszus commented on JCRVLT-688:
----------------------------------------
IMHO the Oak code is only for retrieving the current version at run time, this
can also be used in FileVault when the value needs to be calculated for
new/rewrapped packages. The main question though is where to persist it within
the new/rewrapped package:
# as additional file within META-INF/....
# inside META-INF/MANIFEST.MF inside a certain header
# inside META-INF/vault/properties.xml
# in META-INF/vault/definition/.content.xml only
The reason why the filevault-maven-package-plugin uses the {{builtWith}}
definition is that this is exposed by the AEM CRX Package Manager UI already.
I would propose to go for a new package property (option 3) which would end up
inside a repository anyhow inside the automatically created package definition
and add a dedicated getter method in the API.
Any UI then needs to be adjusted to expose that additional property.
> Add "generator" information to packages generated by filevault
> --------------------------------------------------------------
>
> Key: JCRVLT-688
> URL: https://issues.apache.org/jira/browse/JCRVLT-688
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
>
> It would be nice if packages generated by filevault would carry some
> generator information. That would make it easier to understand what version
> of filevault created a package being debugged.
> (Into META-INF/vault/... I assume?)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
