1 of 2

Should small software libraries avoid using other libraries?

I've just released a small Java library that offers only a few classes and methods. Since I built the project with Maven, I immediately used several third-party libraries to achieve my goals, specifically:

  • commons-lang3 (for some general Java stuff)
  • slf4j-api (for logging)
  • commons-io (for a tiny bit of file stuff - literally reading a file once, I think)

In a normal commercial project for my company I'd think nothing about including (even more) libraries, provided the licences are acceptable. But should I be avoiding using third-party library dependencies when writing my own library for others to use, unless absolutely necessary?

I don't want my library to appear bloated (or arriving with too much baggage) in the eyes of others. What's the normal approach taken here?