[
https://issues.apache.org/jira/browse/ARIA-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032714#comment-16032714
]
Ran Ziv commented on ARIA-264:
------------------------------
Actually, it's possible to first install the plugin, which will also extract it
from its wheel format under the {{PluginManager}}'s working directory, and then
edit and debug the plugin code directly from there.
Not an ideal solution, but it gets the job done :)
> Plugin code debugging capability
> --------------------------------
>
> Key: ARIA-264
> URL: https://issues.apache.org/jira/browse/ARIA-264
> Project: AriaTosca
> Issue Type: Story
> Reporter: Ran Ziv
> Priority: Trivial
>
> Since ARIA requires plugins to be installed in the {{wagon}} format, the code
> is compiled and/or compressed and more difficult to debug on the fly. This
> can complicate the plugin development process.
> Possible ways to ease this difficulty:
> 1) Allow for consumption of plugins in other formats when special
> debug-related flags are used.
> 2) Automate the process of re-wagoning a plugin and replacing it in the
> local plugin repository, thereby allowing users to add remote-debug
> statements to their code and easily redeploy the plugin for debugging.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
