Major Hi Nick, perhaps you can clear this up.
Sometimes I run the dist-diff tool between builds of JBDS to see what changed.
You can see the latest report between JBDS 8.0.0.Beta3b B193 and Beta3c B194 here:
http://machydra.brq.redhat.com/dist-diff/8.0.0.Beta3b-Beta3c/
What is certainly expected are the changes in Forge2 and Webservices - those had fixes in them.
But then you can see many differences like these:
[dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!META-INF/MANIFEST.MF [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!META-INF/ECLIPSE_.SF [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!META-INF/ECLIPSE_.RSA [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!about.mappings
What triggers these is usually a change in the about.mappings file:
nattura:dist-diff rasp$ diff 1/about.mappings 2/about.mappings 6c6 < 0=1.7.2.v20140606-1324 \ No newline at end of file --- > 0=1.7.2.v20140307-0500 \ No newline at end of file
See the different time stamp. In case you wondered, that 0 property is used in the about.properties for build id:
blurb=Eclipse Data Tools Platform Model Base\n\
\n\
Version: {featureVersion}\n\
Build id: {0}\n\
\n\
(c) Copyright Eclipse contributors and others 2005, 2007. All rights reserved.\n\
Visit http://www.eclipse.org/datatools
Do you know why this is happening? Does every build take the dependencies from upstream again and potentially from a different mirror? Is this ok?
