pom.xml:107-109: Get rid of commons-io dependency,...

[dmarkov]

Puzzle 2-b54ace9f in pom.xml:107-109 has to be resolved: Get rid of commons-io dependency, or move it to "test" scope. It's not efficient for such a small and lightweight library to have a big dependency of this kind.

[carlosmiranda]

I know we hate util classes, so what would be the best way of replicating the various IOUtils.toString and FileUtils.toString methods?

I'm thinking of introducing a new package-private class TextResource, which would have four public constructors (reflecting what we use in jcabi-xml):
*TextResource(InputStream stream)
*TextResource(File file)
*TextResource(URL url)
*TextResource(URI uri)

So that, the following uses of commons-io would be:
*IOUtils.toString(stream) -> new TextResource(stream).toString()
*IOUtils.toString(url) -> new TextResource(url).toString()
*IOUtils.toString(uri) -> new TextResource(uri).toString()
*FileUtils.toString(file) -> new TextResource(file).toString()

What do you think?

[yegor256]

The idea is perfect, and the name TextResource is correct, let's do it.

[carlosmiranda]

I created a pull request for it at #18, please review.

[dmarkov]

@carlosmiranda the task is for you now, follow these guidelines. Don't hesitate to ask any technical questions right here

[dmarkov]

@carlosmiranda The budget here is 30 mins, which is exactly how much time will be paid for, when the task is completed

[dmarkov]

@carlosmiranda I added 30 mins to your account, many thanks for working with the project!

[dmarkov]

Finished, thanks, closing..