[
https://issues.apache.org/jira/browse/SLING-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491620#comment-13491620
]
Robert Munteanu commented on SLING-2634:
----------------------------------------
Initial patch which moves to a Command/Result execution model. The changes
performed by the SlingclipseListener are traced . Feel free to use the
information below for tracing and/or to add it to the wiki
h2. Tracing
The operations of the slingclipse plugin are instrumented using the Eclipse
Platform Debug apis. To enable debugging add create a .options file with the
following content
{code}org.apache.sling.slingclipse/debug=true{code]
and then update your eclipse.ini file to contain the following string
{code} -debug
/path/to/.options{code}
The tracing logs will be located in your workspace location at
.metadata/trace.log .
> [Tooling] Slingclipse should expose the operations it performs and their
> results
> --------------------------------------------------------------------------------
>
> Key: SLING-2634
> URL: https://issues.apache.org/jira/browse/SLING-2634
> Project: Sling
> Issue Type: Sub-task
> Components: Extensions
> Reporter: Robert Munteanu
> Assignee: Antonio Sanso
> Priority: Minor
> Attachments: SLING-2634-1.diff, SLING-2634-proof-of-design.diff
>
>
> I think that it's important for the user to know what Slingclipse is doing,
> especially since it uses some heuristics to detect Sling-based projects.
> My first thoughts would be:
> * from a UI point of view start with something simple like a text-only
> console . The subclipse console is a good starting point, we can simply log
> things like
> ADD $SLING_URL $PROJECT/$RESOURCE 200 OK
> REMOVE $SLING_URL $PROJECT/$RESOURCE 500 Internal Server Error
> * from an implementation point of view we could use something like a command
> pattern ( SaveResource command, DeleteResourceCommand ) . This would have the
> benefit of allowing this logging easily + encapsulating the operations for
> batching, handling of offline operations, redo etc.
> Thoughts? I'm willing to look into this, at least for a first iteration.
--
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
