Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
Sling Eclipse IDE 1.0.2
-
None
Description
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.