Tobias Bocanegra commented on JCRVLT-262:

[~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

Reply via email to