Is your feature request related to a problem? Please describe.
Our company has thousands of Java projects. We would like to add Allure to the test class paths of all of them, but we are concerned about library version conflicts from dependencies not directly related to Allure's core functionality. In particular, the jOOR library is pre-1.0 and subject to incompatible API changes, and Apache Tika is about to get a 2.0 release with a commons-io dependency that has known version incompatibilities with older versions.
Describe the solution you'd like
Both Tika and jOOR are used trivially, on exactly one line. Each one can be eliminated easily.
Describe alternatives you've considered
These are used internally and could be shaded, but doing so would increase the jar sizes.
Additional context
As a work-around we have to shade the Allure jars to avoid the unnecessary conflicts.
Is your feature request related to a problem? Please describe.
Our company has thousands of Java projects. We would like to add Allure to the test class paths of all of them, but we are concerned about library version conflicts from dependencies not directly related to Allure's core functionality. In particular, the jOOR library is pre-1.0 and subject to incompatible API changes, and Apache Tika is about to get a 2.0 release with a commons-io dependency that has known version incompatibilities with older versions.
Describe the solution you'd like
Both Tika and jOOR are used trivially, on exactly one line. Each one can be eliminated easily.
Describe alternatives you've considered
These are used internally and could be shaded, but doing so would increase the jar sizes.
Additional context
As a work-around we have to shade the Allure jars to avoid the unnecessary conflicts.