Open tferr opened 11 months ago
Sounds good to me, I'll look into the Windows bundle
Awesome! We can use SNT-v4.3.0-pre-release1 (mapped to 746b1d2de6ad7e40585298252a0efe315c660324) as a freeze point. It includes some minor improvements I had laying around on stalled branches, and more recent work I needed: tweaks to auto-tracing and Weka integration:
@tferr when I try to open Rec. Viewer, I get this error on Windows 11
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load library 'gluegen_rt'
at com.jogamp.common.jvm.JNILibLoaderBase.loadLibraryInternal(JNILibLoaderBase.java:634)
at com.jogamp.common.jvm.JNILibLoaderBase.access$000(JNILibLoaderBase.java:64)
at com.jogamp.common.jvm.JNILibLoaderBase$DefaultAction.loadLibrary(JNILibLoaderBase.java:107)
at com.jogamp.common.jvm.JNILibLoaderBase.loadLibrary(JNILibLoaderBase.java:488)
at com.jogamp.common.os.DynamicLibraryBundle$GlueJNILibLoader.loadLibrary(DynamicLibraryBundle.java:427)
at com.jogamp.common.os.Platform$1.run(Platform.java:321)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.common.util.SecurityUtil.doPrivileged(SecurityUtil.java:82)
at com.jogamp.common.os.Platform.<clinit>(Platform.java:290)
at com.jogamp.opengl.GLProfile.<clinit>(GLProfile.java:154)
at org.jzy3d.chart.Settings.detectProfile(Settings.java:28)
at org.jzy3d.chart.Settings.<init>(Settings.java:13)
at org.jzy3d.chart.Settings.getInstance(Settings.java:58)
at sc.fiji.snt.viewer.Viewer3D.<init>(Viewer3D.java:351)
at sc.fiji.snt.viewer.Viewer3D.<init>(Viewer3D.java:370)
at sc.fiji.snt.viewer.Viewer3D.<init>(Viewer3D.java:381)
at sc.fiji.snt.viewer.Viewer3D.<init>(Viewer3D.java:415)
at sc.fiji.snt.SNTUI$SNTViewer3D.<init>(SNTUI.java:4258)
at sc.fiji.snt.SNTUI$1RecWorker.doInBackground(SNTUI.java:1922)
at sc.fiji.snt.SNTUI$1RecWorker.doInBackground(SNTUI.java:1917)
at java.desktop/javax.swing.SwingWorker$1.call(SwingWorker.java:304)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.desktop/javax.swing.SwingWorker.run(SwingWorker.java:343)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
According to https://jogamp.org/wiki/index.php?title=Maven , the native libraries for all platforms are included with the following maven dependencies
<dependencies>
<dependency>
<groupId>org.jogamp.gluegen</groupId>
<artifactId>gluegen-rt-main</artifactId>
<version>2.3.2</version>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl-all-main</artifactId>
<version>2.3.2</version>
</dependency>
</dependencies>
I tested it in https://github.com/morphonets/SNT/commit/8c9d5f31e6e7c960e1be4cbce80288fdade93272 and it seems to work.
Bummer and weird. That 2.3.2 is the last official version from 2015(!). If I recall correctly, there was patched 2.4.0 version released earlier last year that was pushed to Maven by Jzy3D. I think Curtis worked on that so that our parent scijava pom would use that instead. My understanding is that the 2.4.0 version is the one currently in use by Fiji (JDK8) on all platforms. I predict downgrading it may cause conflicts elsewhere!? Shall we bring this up on Zulip?
I see, yeah we should definitely bring this up
@carshadi , are you able to test Curtis's suggestion: https://imagesc.zulipchat.com/#narrow/stream/327238-Fiji/topic/Problems.20with.20JOGL.20dependencies.20on.20Windows.2011/near/413230673?
This works for me
Curtis' fix added: Let's target https://github.com/morphonets/SNT/releases/tag/SNT-v4.3.0-pre-release2 (21ea56bbfd1b03b744eedf6cfe2662d285d3f1b6)
Hello Tiago, could you publish the 4.3.0-pre-release2?
I'd like to update the Scijava pom and get rid of the exclusions about org.jzy3d:jzy3d-emul-gl
and org.jzy3d:jGL
Hi @elect86,
I don't seem to be able to do a release. I get this error weird javadoc-related error that I cannot make sense, specially since javadoc is disabled in the pom. Also mvn javadoc:javadoc | grep error
detects nothing. Do you know what is causing this?
Would you mind if I give it a try myself?
Not at all, go ahead! Do you need anything from me?
so far no
may I update to the latest Scijava pom 38.0.0-SNAPSHOT?
Sure!
On Thu, Mar 14, 2024, 11:46 Giuseppe Barbieri @.***> wrote:
may I update to the latest Scijava pom 38.0.0-SNAPSHOT?
— Reply to this email directly, view it on GitHub https://github.com/morphonets/SNT/issues/212#issuecomment-1997764018, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASTWDBFTGHVDOAN2QMRGQLYYHA3VAVCNFSM6AAAAABA7ANWFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJXG43DIMBRHA . You are receiving this because you were mentioned.Message ID: @.***>
Could you add me to the repo so that I can create a new branch and work from there instead of forking?
Which tests are supposed to pass with Maven? Because I'm getting weird errors on my machine
Otherwise what passes so far with Gradle is this
@elect86, just sent you the invite. let me know if it something else is needed.
Which tests are supposed to pass with Maven?
The tests that call SNTService
fail because of those net.imagej.patcher.LegacyInjector.preinit();
errors. I can only get those to work on the IDE when I add --add-opens java.base/java.lang=ALL-UNNAMED
. I will probably have to re-write those tests. I added this to the pom after looking around on SO, and I convinced myself that worked to to make the release-script happy.
Indeed, much better now, those 3 looks ignored
Hm, not really. I had convinced myself all tests were passing with 3293439. Will need to look, but I'm in meeting all day. Won't be able to look into it immediately
they all have @Ignore
on them
Anyway, if you want I can publish 4.3.0-pre-release3
If yes, shall I upgrade the pom-scijava to 38.0.0-SNAPSHOT
, 38.0.0
or leave it to 37.0.0
?
I just realized now it's a cyclic dep..
Sure go ahead. bumping it to 38.0.0-SNAPSHOT
is probably a good idea.
Which dependency is cyclic? SNT itself?
SNT and the POM
Published, thanks for your availability Tiago!
Awesome! Did you end up pushing something here? I don't seem to notice any new commits...
In the meanwhile I was waiting for a reply I got eager to try and start working on the fork, then I though I changed the back the remote once I got the invite, but apparently I didn't, it's all here I can push to a gradle
branch here, if you want, the publishing is hardcoded, but if needed, it can be polished and made it smart
Pushed here as well
The next release (v4.3.0) has major changes, notably: minimum Java11 requirement, several changes to auto-tracing and path refining, plus a whole slew of bug-fixes/patches/tweaks. I suspect somethings may break, and it would be useful to plan ahead. Things that we should do:
1121 release)@carshadi, agree? comments?