Robert Munteanu resolved SLING-7501.
    Resolution: Fixed

[~atrsd] - I've updated the dependency to FileVault 3.1.42, it would be great 
to double-check that this fixes your problem. Also please link to the FileVault 
regression as asked by Konrad, so we can better track what caused this. Thanks!

> FilveVault 3.1.38 breaks the Sling IDE Tools "Import from server..."
> --------------------------------------------------------------------
>                 Key: SLING-7501
>                 URL: https://issues.apache.org/jira/browse/SLING-7501
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE, Tooling
>    Affects Versions: Sling Eclipse IDE 1.2.0
>         Environment: All
>            Reporter: Alex Ramos
>            Assignee: Robert Munteanu
>            Priority: Critical
>             Fix For: Sling Eclipse IDE 1.2.2
> Apache Jackrabbit FileVault tool is responsible for Synchronizing files in 
> the File System with content in the JCR repository. Sadly, FileVault version 
> 3.1.38 has a bug that serializes .content.xml file (-the one that contains 
> the node properties-) almost empty.
> Since *AEM plugin for Eclipse* uses Sling-Ide-Tooling internally ([AEM 
> Developer Tools for 
> Eclipse|https://forums.adobe.com/external-link.jspa?url=https%3A%2F%2Fhelpx.adobe.com%2Fexperience-manager%2F6-3%2Fsites%2Fdeveloping%2Fusing%2Faem-eclipse.html]
>  ), and *Sling-Ide-tooling*uses Apache Jackrabbit FileVault tool behind the 
> scenes ([sling-ide-tooling/impl-vlt/src/org/apache/sling/ide at master -  
> apache/sling-ide-tooling -  
> GitHub|https://forums.adobe.com/external-link.jspa?url=https%3A%2F%2Fgithub.com%2Fapache%2Fsling-ide-tooling%2Ftree%2Fmaster%2Fimpl-vlt%2Fsrc%2Forg%2Fapache%2Fsling%2Fide]
>  ), we end up having that same issue (-almost empty .content.xml files-) when 
> using AEM plugin for Eclipse.
> This issue is also discussed here: 
> [https://forums.adobe.com/message/10181131#10181131]
> Upgrading to FileVault 3.1.42 (latest) is recommended.

This message was sent by Atlassian JIRA

Reply via email to