[
https://issues.apache.org/jira/browse/SLING-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-4000.
------------------------------------
Resolution: Fixed
> Add error marker on the project when content sync root does not exist
> ---------------------------------------------------------------------
>
> Key: SLING-4000
> URL: https://issues.apache.org/jira/browse/SLING-4000
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.2
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.4
>
>
> Various scenarios can lead to a content project not having the content sync
> root correctly configured:
> - moving the directory ( although we could hook in a refactoring participant
> ... )
> - having a non-standard location and then copying the project to a new
> workspace ( the property is per-workspace, not saved in the .settings
> directory )
> To prevent this and other problems, we should add an error marker on the
> project if the content sync root does not exist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
