[shrinkwrap-issues] [JBoss JIRA] Reopened: (SHRINKWRAP-235) Add print methods to Archive

[Dan Allen (JIRA)]

     [ https://issues.jboss.org/browse/SHRINKWRAP-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Allen reopened SHRINKWRAP-235:
----------------------------------



Upon further review, we've got a new proposal. I still feel that the System.out.println() breaks the spirit of ShrinkWrap's fluid API. So instead, let's think about a more general purpose for these methods.

What we really want to do is write to a stream. So, how about this API

writeTo(Stream, Formatter)

Then we can do something like:

archive.writeTo(System.out, Formatter.VERBOSE)

This is more in spirit with the zip exporters where we are pushing the archive through to a stream in some way. We are exporting the view of the archive in essence.

> 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
>
> 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