[
https://issues.jboss.org/browse/SHRINKWRAP-235?page=com.atlassian.jira.pl...
]
Andrew Rubinger commented on SHRINKWRAP-235:
--------------------------------------------
I always thought Exception.prinkStackTrace was a bad idea. Reason being: Streams write
things. Things don't write themselves. I'd like to discuss this one a bit.
Also, usually System.out is an odd default target; usually it's a logger, not some
stream directly.
Add print methods to Archive
----------------------------
Key: SHRINKWRAP-235
URL:
https://issues.jboss.org/browse/SHRINKWRAP-235
Project: ShrinkWrap
Issue Type: Feature Request
Components: api, impl-base
Affects Versions: 1.0.0-alpha-11
Reporter: Dan Allen
Priority: Minor
Fix For: 1.0.0-alpha-12
An extremely common use case for the "toString" methods on Archive are to print
the contents of the Archive to stdout.
System.out.println(archive.toString(true));
Having to wrap the call in System.out.println is really annoying (even with editor
shortcuts). ShrinkWrap should provide parallel print methods, that print to stdout (or
perhaps to an optional stream argument).
archive.print()
archive.print(true)
archive.print(Formatter)
* parallel methods that accept a stream if warranted
* I'd also settle for printArchive()
This feature is consistent with the ever popular Exception#printStackTrace().
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira