Robert Munteanu created SLING-2634:
--------------------------------------
Summary: [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
Priority: Minor
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
