You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/07/16 22:37:04 UTC

[jira] [Commented] (SLING-3766) Importing an existing content project does not reveal the content navigator

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

Robert Munteanu commented on SLING-3766:
----------------------------------------

I think I know what happens. The project initially had an invalid content sync directory value ( jcr_root ) but the content was at src/main/content/jcr_root. A refresh fixed it, but we probably need to react to changes in the value of the content sync root property

> Importing an existing content project does not reveal the content navigator
> ---------------------------------------------------------------------------
>
>                 Key: SLING-3766
>                 URL: https://issues.apache.org/jira/browse/SLING-3766
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>            Reporter: Robert Munteanu
>            Priority: Minor
>             Fix For: Sling Eclipse IDE 1.1.0
>
>
> Just noticed that if I import a zipped content project, with all the Eclipse project files properly set up, the content sync root is shows as a filesystem structure, not with our nice navigator.
> [~egli] - this would be nice to have for 1.0.2 if  it's a quick fix. Otherwise we'll leave it for 1.1.0 .



--
This message was sent by Atlassian JIRA
(v6.2#6252)