[FELIX-4921] Ensure binary equality of the same bundle between successive DM releases

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: org.apache.felix.dependencymanager-r5
• Fix Version/s: org.apache.felix.dependencymanager-r6
• Component/s: Dependency Manager, Dependency Manager Annotations, Dependency Manager Runtime, Dependency Manager Samples, Dependency Manager Shell
• Assignee: Pierre De Rop
• Reporter: Pierre De Rop
• Created: 11/Jun/15 22:26
• Updated: 30/Nov/15 12:55
• Resolved: 11/Jun/15 22:55

Description

As reported by Bram in the vote for the DM release R4 (see [1]); when a new DM release R is made, and if that new release contains an unmodified bundle since the previous R-1, then the new release R includes a rebuilt version of the unmodified bundle.

While this is not a real issue, it turns out that there is still a binary difference for the same bundle between R-1 and R.
Even is we don't include headers like "Bnd-LastModified,Tool,Created-By", there may be a binary diff (because the jar has been rebuilt).

As suggested by Bram, when a bundle is unmodified, it would be better to just use the same binary version from the release repo instead of using the just rebuilt version. This will ensure binary equality for an unmodified bundle between successive DM releases.

[1] http://www.mail-archive.com/[e-mail]/msg36806.html