René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Shade all implementation dependencies","articleBody":"**Is your feature request related to a problem? Please describe.**\r\n\r\nAllure unexpected upgraded Jackson from the 2.11.x family to the 2.12.x family. A bug-fix related to incorrect serialization of Java 8 times caused failures in tests.\r\n\r\n**Describe the solution you'd like**\r\n\r\nIdeally, _all_ dependencies that are not _required_ to be exposed to Allure user should be shaded, repackaged to a non-standard location and placed in the Allure jars. This would remove them from the Allure dependencies and prevent such problems in the future.\r\n\r\n**Describe alternatives you've considered**\r\n\r\nSimply removing the dependencies entirely would be even better, as was recently done for jOOR and Tika, as was done in #595, but this is likely impractical for Jackson and others.\r\n\r\n**Additional context**\r\n\r\nWe are attempting to inject Allure into our Java build process for 1,000s of different projects. While we attempt to have some consistency in versioning, there are so many edge cases that there are exceptions to almost everything. Having very common dependencies like Jackson be pinned by Allure make it extremely difficult to use broadly. We have temporarily modified our build rules to ignore the version of Jackson requested by Allure, but this is likely not a sustainable solution.\r\n","author":{"url":"https://github.com/mkw","@type":"Person","name":"mkw"},"datePublished":"2021-06-22T17:49:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/609/allure-java/issues/609"}