[jira] [Comment Edited] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages
[ https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16351918#comment-16351918 ] Tobias Bocanegra edited comment on JCRVLT-262 at 2/5/18 1:50 AM: - [~kwin] the comments regarding the regressions mentioned above are not relevant to this issue. further is the product management of Adobes AEM out of scope of an apache project and should be discussed using the appropriate channels offered by Adobe. bq. Actually the generated package is now closer to what the package manager would generate since the package manager always uses Extended File Aggregates ...which is something I would rather get rid off, and provide the sub-packages outside the jcr content. this is also problematic for setups with changed package root or systems where the packages are not stored in the JCR at all. was (Author: tripod): [~kwin] the comments regarding the regressions mentioned above are not relevant to this issue. further is the product management of Adobes AEM out of scope of an apache project and should be discussed using the appropriate channels offered by Adobe. bq. Actually the generated package is now closer to what the package manager would generate since the package manager always uses Extended File Aggregates ...which is something I would rather get rid off, as well, since some of the information is duplicated in the properties, MANIFEST, filter.xml, etc. I would rather provide a better way to convey the missing meta information differently. however, I see that it might be beneficial to support the population of the definition node properly, since many users want to include this extra information into the package via maven. > 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)
[jira] [Comment Edited] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages
[ https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330167#comment-16330167 ] Konrad Windszus edited comment on JCRVLT-262 at 2/2/18 5:27 PM: There are several issues with upgrading: # all releases since 3.1.38 suffered from pretty serious regressions, namely https://issues.apache.org/jira/browse/JCRVLT-186 in 3.1.40 and https://issues.apache.org/jira/browse/JCRVLT-258 in both 3.1.40 and 3.1.42 # Adobe does not provide an official hotfix in its commercial product AEM containing a newer version Apart from that the workaround does not do any harm (even in newer instances). It just switches from "Simple File Aggregates" for sub packages to "Extended File Aggregates" (http://jackrabbit.apache.org/filevault/vaultfs.html). Actually the generated package is now closer to what the package manager would generate since the package manager always uses Extended File Aggregates. was (Author: kwin): There are several issues with upgrading: # all releases since 3.1.38 suffered from pretty serious regressions, namely https://issues.apache.org/jira/browse/JCRVLT-186 in 3.1.40 and https://issues.apache.org/jira/browse/JCRVLT-258 in both 3.1.40 and 3.1.42 # Adobe does not provide an official hotfix in its commercial product AEM containing a newer version Apart from that the workaround does not do any harm (even in newer instances). It just switches from "Simple File Aggregates" for sub packages to "Extended File Aggregates" (http://jackrabbit.apache.org/filevault/vaultfs.html) > 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)
[jira] [Comment Edited] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages
[ https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328691#comment-16328691 ] Konrad Windszus edited comment on JCRVLT-262 at 1/17/18 12:46 PM: -- The proposed workaround would place a {{.content.xml}} in a sibling folder to the subpackage's zip named {{}} having the following content {code} http://www.jcp.org/jcr/1.0; jcr:primaryType="nt:file"> {code} was (Author: kwin): The proposed workaround would place a {{.content.xml}} in a sibling folder to the ZIP named {{}} having the following content {code} http://www.jcp.org/jcr/1.0; jcr:primaryType="nt:file"> {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)
[jira] [Comment Edited] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages
[ https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328691#comment-16328691 ] Konrad Windszus edited comment on JCRVLT-262 at 1/17/18 12:46 PM: -- The proposed workaround would place a {{.content.xml}} in a sibling folder to the ZIP named {{}} having the following content {code} http://www.jcp.org/jcr/1.0; jcr:primaryType="nt:file"> {code} was (Author: kwin): The proposed workaround would place a {{.content.xml}} in a sibling folder to the ZIP named {{}} having the following content {code} 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"> {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)