Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Ensure third party dependency versions match across POMs and update site #38
Some third party dependencies have a different version uploaded to the Fiji update site than is declared in Maven POM(s). This results in a "Locally modified" discrepancy for that library. Whenever we are using release bindings (and we indeed always use release bindings for third party dependencies) we should make sure that the POMs always reflect the version uploaded to the update site.
The first step to addressing this ticket is to build Fiji from source and make an thorough list of affected JARs. I am confident there are at least a few, but of course we need to be explicit about which JARs are skewed in this way.