[jira] [Commented] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

["Konrad Windszus (JIRA)" <ji...@apache.org>]

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

Konrad Windszus commented on JCRVLT-262:
----------------------------------------

The proposed workaround would place a {{.content.xml}} in a sibling folder to the ZIP named {{<packagename.zip.dir>}} having the following content

{code}
<?xml version="1.0" encoding="UTF-8"?>
<!-- necessary due to https://issues.apache.org/jira/browse/JCRVLT-177, otherwise stale filter and dependencies would be considered -->
<jcr:root xmlns:vlt="http://www.day.com/jcr/vault/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"
    jcr:primaryType="nt:file">
    <jcr:content
        jcr:primaryType="nt:resource"/>
</jcr:root>
{code}

> Implement workaround for JCRVLT-177 when creating subpackages
> -------------------------------------------------------------
>
>                 Key: JCRVLT-262
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-262
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: package maven plugin
>    Affects Versions: package-maven-plugin-1.0.1
>            Reporter: Konrad Windszus
>            Priority: Major
>
> Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of subpackages are not correctly overwritten (when updating a SNAPSHOT version package with Jackrabbit Filevault < 3.1.40).
> The workaround to create subpackages not only as one Simple File (the .zip) but also creating an according .content.xml works around this limitation and leads to correctly updating the meta data. The Maven plugin should allow to optionally create the .content.xml along with the subpackage automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)