You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2017/12/05 12:51:00 UTC

[jira] [Commented] (JCRVLT-230) Allow to give an explicit directory as source for META-INF/vault

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

Stefan Seifert commented on JCRVLT-230:
---------------------------------------

in wcm.io content package plugin we used a folder {{src/main/package-definition}} as default folder for things like filter.xml and thumbnail.png.

> Allow to give an explicit directory as source for META-INF/vault
> ----------------------------------------------------------------
>
>                 Key: JCRVLT-230
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-230
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: package maven plugin
>    Affects Versions: package-maven-plugin-1.0.0
>            Reporter: Konrad Windszus
>
> Currently the {{META-INF/vault}} structure within the packages is built from {{<workDirectory>/META-INF/vault}}.
> This directory is used for two purposes
> # It receives the generated filter.xml, the merged properties.xml, the config.xml and the settings.xml
> # It acts as a source for the resulting package's META-INF/vault
> Not all meta files below META-INF/vault are being generated through the plugin itself. Some need to be written manually to {{workDirectory}} with the help of the {{maven-resource-plugin}}.
> It would be good to allow to give an explicit source directory for the META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from {{workDirectory}}. This would allow to e.g. specify the packages thumbnail image, without being forced to copy it over to from src to target.
> In addition this parameter should clearly define which meta files are generated by the filevault-package-maven-plugin and are therefore never considered, even if they are located in the given META-INF/vault source directory.



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