Pierre De Rop created FELIX-4921:
------------------------------------
Summary: Ensure binary equality of the same bundle between
successive DM releases
Key: FELIX-4921
URL: https://issues.apache.org/jira/browse/FELIX-4921
Project: Felix
Issue Type: Improvement
Components: Dependency Manager, Dependency Manager Annotations,
Dependency Manager Runtime, Dependency Manager Samples, Dependency Manager Shell
Affects Versions: org.apache.felix.dependencymanager-r5
Reporter: Pierre De Rop
Assignee: Pierre De Rop
Priority: Trivial
Fix For: org.apache.felix.dependencymanager-r6
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/[email protected]/msg36806.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
