Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 16 17:34
    acardona opened #231
  • Aug 07 13:48
    chalkie666 opened #230
  • Aug 02 13:33
    tinevez labeled #107
  • Aug 02 13:33
    tinevez labeled #107
  • Aug 02 13:32
    tinevez opened #107
  • Aug 02 13:30
    tinevez commented #106
  • Aug 02 13:29
    tinevez synchronize #106
  • Aug 02 13:29

    tinevez on serialize-feature-model2

    Avoid feature name inflation wh… Update the MaMuT exporter examp… (compare)

  • Jul 18 11:57
    tpietzsch commented #106
  • Jul 18 11:44
    tinevez commented #106
  • Jul 18 11:41
    tpietzsch commented #106
  • Jul 18 11:32
    tinevez commented #106
  • Jul 18 11:31
    tpietzsch commented #106
  • Jul 18 11:20
    tpietzsch synchronize #106
  • Jul 18 11:20

    tpietzsch on serialize-feature-model2

    formatting Demonstrate that feature names … Add TODO and 2 more (compare)

  • Jul 10 13:08
    tinevez closed #104
  • Jul 10 13:08
    tinevez commented #104
  • Jul 10 13:08
    tinevez opened #106
  • Jul 10 10:56

    tinevez on serialize-feature-model2

    Fix weird compile error with Op… Make some static methods of MaM… JUnit test for the TrackMate im… and 5 more (compare)

  • Jul 09 11:01

    tinevez on serialize-feature-model2

    Move test data to proper packag… WIP: Junit test for MaMuT expor… (compare)

Jean-Yves Tinevez
@tinevez
@ctrueden Is it something I could do about the 3.0.0 version of TrackMate? Could I release a new version with a proper 2.9.0 (for instance) without breaking everything?
Curtis Rueden
@ctrueden
It comes down to the fact that SemVer is incompatible with "romantic versioning"
In other words: you cannot hold off on 3.0.0 forever—SemVer demands the major version bump whenever some backwards incompatible change occurs.
One way people get around this is to use four digits: with the leftmost being the "romantic" one.
I.e.: the marketing one: big huge change with everything new!
I apologize that a TrackMate 3.0.0 was necessary, but IIRC it was needed due to the Java 3D changes.
One option is not to use the numeral for the new version of TrackMate, but instead "TrackMateX" or something. Or: just don't worry about it, and rebrand the artifact as TrackMate again once it is ready, with the next major version digit.
I don't have all the answers here: otherwise we wouldn't have a thing called "ImageJ2" ... :worried:
Stefan Helfrich
@stelfrich
Thanks to you @ctrueden, I will never stop learning new things, like "sentimental versioning”. :clap:
Curtis Rueden
@ctrueden
Hehehe
tpietzsch
@tpietzsch
Speaking of TrackMate3: YEsterday, trying to demo it, I ran into the Java8-Fiji issue
I had told people to update Fiji beforehand, but that doesn't bring in the java8 updates.
Can someone point me to best practices or something on the wiki?
I guess: Reinstall Fiji?
Stefan Helfrich
@stelfrich
Had a similar issue today. Only solution: reinstall
tpietzsch
@tpietzsch
Ok
I thought so
...
Stefan Helfrich
@stelfrich
I couldn’t even get any error message..
tpietzsch
@tpietzsch
Oh... then you ran into something different
Stefan Helfrich
@stelfrich
Oh.. nice..
tpietzsch
@tpietzsch
for me the issue was clearly that Fiji was still running with java 1.6
:-D
major.minor version exception thingie
Stefan Helfrich
@stelfrich
Then hope might not be lost.. I had a Fiji that did not start at all after enabling the Java8 update site..
Jean-Yves Tinevez
@tinevez
@ctrueden The Jenkins job is in Java8 right?
Because I have a couple of Eclipse warnings like for example
JList is a raw type. References to generic type JList<E> should be parameterized
I would like to get rid of. Is it safe for an artifact that is under Jenkins supervision?
Curtis Rueden
@ctrueden
@tinevez Which Jenkins job?
Looks like that job is currently set to build using Java 6.
@tpietzsch @stelfrich There is no migration guide from Java 6 to Java 8 yet.
The easiest solution is to redownload Fiji. Alternately, you can download Fiji then rip out the java folder and stuff it into your existing installation, overwriting the old one (or renaming the old one to e.g. java6).
Then you can turn on the Java-8 update site and it should work without needing to reinstall. This is nice if your Fiji is complex with lots of manually added stuff.
I do not have time to make the updater support Java version upgrades, unfortunately.
Curtis Rueden
@ctrueden
@tinevez I changed the MaMuT Jenkins job to use Java 8 now, since it looks like the latest code requires it.
Jean-Yves Tinevez
@tinevez
thanks @ctrueden .
I might crash things in the next hours.
Jean-Yves Tinevez
@tinevez
Turns out things are really smooth with the Java8 thingie. This is the first time the 3D Viewer in TrackMate and MaMuT works in a long time.
Plus it made me review the code a bit. Thanks @ctrueden
Curtis Rueden
@ctrueden
Very glad to hear that!
BTW, I saw that the TrackMate job failed, so I bumped it to use Java 8 instead of 7 now, which addressed the issue.
Jean-Yves Tinevez
@tinevez
Thanks!
Stefan Helfrich
@stelfrich
I remember a discussion about discovering available Java version on a system in the context of switching to Java 8. Does that code work reliably? If so, where does it live?
Curtis Rueden
@ctrueden
@stelfrich github.com/imagej/imagej-launcher but we will likely be retiring it.
Stefan Helfrich
@stelfrich
@ctrueden I was asking because I blew a Fiji installation with enabling the Java 8 update site (as mentioned before) without having a Java 8 installation on the machine (not having properly read the news post on the topic). I was wondering if we could have a check for an exisiting Java 8 installation before enabling the Java 8 update-site.
(although I guess you have thought about that and it is not quite as easy as I imagine..)
Curtis Rueden
@ctrueden
@stelfrich We could hardcode something, I guess.
Stefan Helfrich
@stelfrich
idk. it might be useful for the next months?
Curtis Rueden
@ctrueden
I want this all to be over with before the "next months" have passed.