[
https://issues.apache.org/jira/browse/SLING-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735345#comment-13735345
]
Robert Munteanu edited comment on SLING-2973 at 8/9/13 9:39 PM:
----------------------------------------------------------------
[~kwin] - I've refreshed the p2 update site, now that SLING-2267 is fixed. You
can open a console view ( named 'Sling console' ) which will output the
operations in more detail. Let me know how that works for you.
That being said, I don't expect this to be usable with CQ right now, because:
* we don't yet interoperate with VLT
* we don't yet interpret .content.xml files properly
What _might_ work is defining a filters.txt file in the directory below
jcr_root and whitelisting files you want to sync.
(Edit: typo)
was (Author: rombert):
[~kwin] - I've refreshed the p2 update site, now that SLING-2267 is fixed.
You can open a console view ( named 'Sling console' ) which will output the
operations in more detail. Let me know how that works for you.
That being said, I don't expect this to be usable with CQ right now, because:
* we don't yet interoperate with VLT
* we don't yet interpret .content.xml files properly
What _might_ works is defining a filters.txt file in the directory below
jcr_root and whitelisting files you want to sync.
> [Tooling] Align Eclipse tooling to proposed structure
> -----------------------------------------------------
>
> Key: SLING-2973
> URL: https://issues.apache.org/jira/browse/SLING-2973
> Project: Sling
> Issue Type: Sub-task
> Components: IDE
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> The current IDE tooling needs to be aligned to the structure defined at [1] .
> We should be careful to preserve existing behaviour, but regressions in the
> short run are acceptable since we will move to the WST framework, which is a
> different beast altogether.
> [1]: https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling
--
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
