[ERROR] Filter root's ancestor '/apps' is not covered by any of the specified dependencies. | Community
Skip to main content
rajeev_yadav
Level 4
Aug 21, 2018 2:29 PM UTC
Solved

[ERROR] Filter root's ancestor '/apps' is not covered by any of the specified dependencies.

I am trying to upgrade content  package plugin from 0.0.24 to 0.5.24. When trying to build code with upgraded version, I am getting below build errors:

[ERROR] Filter root's ancestor '/apps' is not covered by any of the specified dependencies.

My filter.xml looks like:

<?xml version="1.0" encoding="UTF-8"?>

<workspaceFilter version="1.0">

    <filter root="/apps/foo"  />

</workspaceFilter>

Anyone experienced this issue or knows on what could be the reason here?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
arunpatidar
arunpatidarAccepted solution
New Participant
Aug 21, 2018 2:54 PM UTC

Hi,

Could you problem due updating existing archetype with new version, but not sure. Can you try 0.5.1 working for me. I tried both latest 0.5.24 and 1.0.2 versions with archetype 11 not working for me as well.

Arun Patidar
View reply

6 replies

KaushikNitin
Level 2
Oct 20, 2020 1:32 PM UTC

Add valid roots[1] or disable[2] it .
[1] <configuration>
<packageType>application</packageType>
<validatorsSettings>
<jackrabbit-filter>
<options>
<validRoots>/apps/myapp</validRoots>
</options>
</jackrabbit-filter>
</validatorsSettings>
</configuration>
[2]
<configuration>
<packageType>mixed</packageType>
<validatorsSettings>
<jackrabbit-packagetype>
<isDisabled>true</isDisabled>
</jackrabbit-packagetype>
</validatorsSettings>
</configuration>

Translate
    smacdonald2008
    smacdonald2008
    Level 10
    Aug 21, 2018 3:12 PM UTC

    Report that bug to cust care by opening a ticket so it can get fixed. In mean time - use the version that builds and works in your AEM environment.

    Translate
    rajeev_yadavAuthor
    Level 4
    Aug 21, 2018 3:10 PM UTC

    Scott - I changed it to 0.5.1 .. but somewhere I read that 0.5.24 is stable release.. In future if we try to upgrade it then it would good if this bug is fixed.

    Translate
    smacdonald2008
    smacdonald2008
    Level 10
    Aug 21, 2018 3:08 PM UTC

    I recommend using the version that works.

    Translate
    rajeev_yadavAuthor
    Level 4
    Aug 21, 2018 3:01 PM UTC

    Thanks Arun. It is building fine with 0.5.1.

    Could it be bug in 0.5.24?

    Translate
    arunpatidar
    arunpatidarAccepted solution
    New Participant
    Aug 21, 2018 2:54 PM UTC

    Hi,

    Could you problem due updating existing archetype with new version, but not sure. Can you try 0.5.1 working for me. I tried both latest 0.5.24 and 1.0.2 versions with archetype 11 not working for me as well.

    Translate
    Arun Patidar
    Terms & ConditionsAccessibility statement

    Loading footer...