Community
Participate
Working Groups
3.7 RC4. When the comparator reports a problem about file count differences then this might be caused by signing issues. The log could provide that hint to help people tracking down the issue. See e.g. http://download.eclipse.org/eclipse/downloads/drops/S-3.7RC4-201106030909/buildlogs/comparatorlog.txt.
Almost every comparator error is a file count difference, or a difference in class files or something similar. I think I'll just link a wiki entry from the build page on how to interpret comparator errors. The log is generated by p2 tooling, not releng tools.
This bug belongs to p2. It appears that for features (JarComparator#compareFeatures) uou get one message "The feature has a different number of entries" followed by multiple "The entry \"{0}\" is not present in both features" Something similar should be done when comparing bundles. Currently JarComparator#compare(File, File) is fail-fast when the number of entries is not the same. This can be changed to be the same as how we treat features.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
