New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure third party dependency versions match across POMs and update site #38

Open
ctrueden opened this Issue Oct 21, 2013 · 0 comments

Comments

Projects
None yet
2 participants
@ctrueden
Member

ctrueden commented Oct 21, 2013

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment