[MGNLDIFF-11] Repackage Daisydiff Created: 11/Apr/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Diff Module
Component/s: None
Affects Version/s: None
Fix Version/s: Backlog

Type: Task Priority: Neutral
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
supersedes MGNLDIFF-8 bundled daisy diff jar should not inc... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Following MGNLDIFF-8, a better fix might be to repackage daisydiff, and "relocate" its dependencies: see http://maven.apache.org/plugins/maven-shade-plugin/examples/class-relocation.html

As a first step, we'll probably need to do this as an own project (i.e repackage the existing daisydiff, producing our own artifact). A second step would be to contribute this back to the daisydiff developers.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 05:20:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.