You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you. I included the library and the error message is gone. Before posting here I did try that but with a more recent version of slf4j and that did not work. Maybe you should make a note about this on the front page for other users.
Thank you. I included the library and the error message is gone. Before posting here I did try that but with a more recent version of slf4j and that did not work. Maybe you should make a note about this on the front page for other users.
This will depend where you get the library. On our downloads page, it should never appear however from Maven it will. This is because Maven requires the transient dependencies to be resolved by the build system whereas our download should contain everything needed to use the library.
Where did you download it from? If it was from our downloads area, that's a bug.
This is the same as #76. It should not be a critical problem, so if it prevents you from opening port, please share more details / stack trace.
This seems to be accurate. Here's my output:
- SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".- SLF4J: Defaulting to no-operation (NOP) logger implementation- SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[/dev/cu.Bluetooth-Incoming-Port, /dev/cu.wlan-debug, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.wlan-debug]
No exceptions are thrown in this example. I believe the long-term plan is to remove native-lib-loader as a project dependency which will remove the transient dependency on slf4j. With regards to documenting this, we're welcome to recommendations on how to present this to the user on the project page.
Activity
pietrygamat commentedon Jan 4, 2024
This is the same as #76. It should not be a critical problem, so if it prevents you from opening port, please share more details / stack trace.
athach commentedon Jan 4, 2024
Thank you. I included the library and the error message is gone. Before posting here I did try that but with a more recent version of slf4j and that did not work. Maybe you should make a note about this on the front page for other users.
tresf commentedon Jan 4, 2024
This will depend where you get the library. On our downloads page, it should never appear however from Maven it will. This is because Maven requires the transient dependencies to be resolved by the build system whereas our download should contain everything needed to use the library.
Where did you download it from? If it was from our downloads area, that's a bug.
athach commentedon Jan 5, 2024
It was downloaded from https://github.com/java-native/jssc/releases/tag/v2.9.6
tresf commentedon Jan 10, 2024
@athach from my testing against v2.9.6, this is not an Exception, but rather a benign message logged to stderr. Here's my code:
This seems to be accurate. Here's my output:
No exceptions are thrown in this example. I believe the long-term plan is to remove native-lib-loader as a project dependency which will remove the transient dependency on slf4j. With regards to documenting this, we're welcome to recommendations on how to present this to the user on the project page.
athach commentedon Jan 11, 2024
I am sorry. You are correct, it is not an exception.
Replace scijava native-lib-loader with jssc.NativeLibraryLoader (B-10)
Replace scijava native-lib-loader with jssc.NativeLibraryLoader (B-10)