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

Fiji built from source has discrepancies with the Fiji user distribution #39

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

Comments

Projects
None yet
3 participants
@ctrueden
Member

ctrueden commented Oct 21, 2013

This issue describes a blanket problem that we may want to file into separate issues on a per-artifact basis. There will always be some discrepancies between what is built from source (i.e., the latest master branch) and what has been uploaded to the updater (i.e., the latest tested-and-working binaries). This is a good thing.

However, at the time of this writing, there are actually many discrepancies that cannot be explained by differences in the Fiji source code itself.

  1. One reason is certain dependencies present on the Fiji update site, but upon which no component of Fiji explicitly depends. See issue #37.

  2. Some third party JAR versions do not match between Maven POM(s) and the Fiji update site. See issue #38.

  3. Fiji has quite a few SNAPSHOT version couplings, which we likely want to phase out over time. But within fiji.git itself those couplings are very convenient, so we should carefully consider what the best approach is.

  4. There are potentially other reasons for these discrepancies, which would be brought to light by an thorough examination of all differing files identified by the ImageJ updater.

@dscho dscho self-assigned this Mar 22, 2014

@dscho dscho removed their assignment Nov 9, 2014

@ctrueden ctrueden self-assigned this Jan 14, 2015

@ctrueden

This comment has been minimized.

Show comment
Hide comment
@ctrueden

ctrueden Jan 14, 2015

Member

We are getting very close to the fiji.git build matching what is distributed on the Fiji update site. (See e.g. 04f283a.) Once we achieve that convergence, we can actually drive the Fiji update site by what's currently on fiji.git master, using Jenkins!

Member

ctrueden commented Jan 14, 2015

We are getting very close to the fiji.git build matching what is distributed on the Fiji update site. (See e.g. 04f283a.) Once we achieve that convergence, we can actually drive the Fiji update site by what's currently on fiji.git master, using Jenkins!

@hinerm

This comment has been minimized.

Show comment
Hide comment
@hinerm

hinerm Feb 6, 2015

Member

Known roadblocks:

  • Current LSM_Toolkit version (4.0g) has snapshot parent
Member

hinerm commented Feb 6, 2015

Known roadblocks:

  • Current LSM_Toolkit version (4.0g) has snapshot parent

ctrueden referenced this issue in fiji/pom-fiji Feb 6, 2015

Bump components to releases on Fiji update site
The following component versions are present on the update site:
* TrackMate_ 2.7.1
* Trainable_Segmentation 2.1.8

Hence, these should also be the versions declared in pom-fiji.

See: fiji/fiji#37

ctrueden referenced this issue Apr 20, 2015

Add a mechanism to autorun JavaScript files
JS files are placed in plugins/Scripts/Plugins/AutoRun/, thus showing up in an
entry called "AutoRun" in the "Plugins" menu.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment