[ 
https://issues.apache.org/jira/browse/GSHELL-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548525
 ] 

Jason Warner commented on GSHELL-46:
------------------------------------

I just type up a whole long thing for this and then lost it when I clicked add 
and my session had timed out, so I'll be brief.  I found I can get the 
exception stack traces by setting the verbosity level to "VERBOSE".  I'm not 
sure if this is what you were looking for or not, even though it seems to 
accomplish the goal.  My only issue is that the only difference between this 
and --verbose is --verbose also alters the log level.  

I also looked into setting a system property.  Assuming changing the verbosity 
is sufficient, it would only be a matter of checking this property at set 
points and then changing the verbosity accordingly.  I thought this check could 
be done on ever output, but then realized that output is done through 
PrintWriters that have already been defined.  Is there a good place to perform 
this check?  If you don't actually know of a place off hand, let me know and 
I'll do my own leg work.  I just thought it'd be fun to leverage the knowledge 
of someone with a ton more GShell experience than myself.

Finally, I like the idea of persistent options loaded from the preferences but 
think that probably should be covered in a separate jira as it's work effort is 
outside the scope of this one.  If there isn't one already, I'll open one up 
myself.

Ok, that wasn't too brief.  My mistake.



> Add flag to show exception stacktraces
> --------------------------------------
>
>                 Key: GSHELL-46
>                 URL: https://issues.apache.org/jira/browse/GSHELL-46
>             Project: GShell
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: CLI
>    Affects Versions: 1.0-alpha-1
>            Reporter: Jason Dillon
>            Assignee: Jason Warner
>            Priority: Trivial
>             Fix For: 1.0-alpha-2
>
>
> Add a flag to the main CLI to show exception stacktraces (like mvn -e)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to