[jira] [Commented] (SLING-2660) [Tooling] Add a Sling project nature to control projects being synchronized

["Robert Munteanu (JIRA)" <ji...@apache.org>]

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

Robert Munteanu commented on SLING-2660:
----------------------------------------

Added a first patch which moves from a global resource listener and the early startup implementation to a nature + builder . I've tried to minimise code changes for this version so it's easier to review.

Pending change

- the code still delegates to the visitor from the SlingclipseListener class, but the logic will be moved to its own class since we don't use listeners anymore

Open issue

- I've added new classes to an {{.internal}} package since they should not be exported ; but I noticed that we don't use export any packages so that's reversible
                
> [Tooling] Add a Sling project nature to control projects being synchronized
> ---------------------------------------------------------------------------
>
>                 Key: SLING-2660
>                 URL: https://issues.apache.org/jira/browse/SLING-2660
>             Project: Sling
>          Issue Type: Sub-task
>          Components: Extensions
>            Reporter: Robert Munteanu
>         Attachments: SLING-2660.diff
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> From a usability point of view it's better to have a Sling project nature which allows users to opt-in to their resources being synchronized and also could allow defining repositories per project, as opposed to global projects.
> I'll try and look into this in the coming days.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira