Hi J-Y, >Woops sorry I did not know.
When TrackMate 2.5.0 was released there actually wasn't a pom-fiji release to pin to.. so don't be too hard on yourself. :) >How can I fix this? You could update TrackMate's parent pom to the latest pom-fiji release <https://github.com/fiji/pom-fiji/releases>. However, that beta-0 release is fairly old (last commit is from July 24th) so you may need something more recent. Also, it doesn't completely solve the issue since you do have other sc.fiji dependencies in TrackMate... so until we convert everything to a release coupling, things won't truly be stable and reproducible. Johannes is out for the weekend.. I will talk with him on Monday about how we want to release pom-fiji:beta-1, and transition everything to release couplings. Regards, Mark On Fri, Oct 3, 2014 at 2:54 PM, Jean-Yves Tinevez <tine...@pasteur.fr> wrote: > > OK, I finally made a little time to look at this. >> >> Yes, this is a major problem with TrackMate's releases. Version 2.5.0 >> inherits from sc.fiji:pom-fiji:2.0.0-beta-1-SNAPSHOT. This is forbidden >> in Maven terms -- a release must depend only on other releases. >> > > > > Woops sorry I did not know. > How can I fix this? > best > jy > > --- > This email is free from viruses and malware because avast! Antivirus > protection is active. > http://www.avast.com > > > > _______________________________________________ > ImageJ-devel mailing list > ImageJ-devel@imagej.net > http://imagej.net/mailman/listinfo/imagej-devel >
_______________________________________________ ImageJ-devel mailing list ImageJ-devel@imagej.net http://imagej.net/mailman/listinfo/imagej-devel
