8000 Exclude Jpype 1.5.1 · Issue #70 · scijava/scyjava · GitHub
[go: up one dir, main page]
Skip to content

Exclude Jpype 1.5.1 #70

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.

Sign up for GitHub

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

Jump to bottom
Closed
hinerm opened this issue Dec 3, 2024 · 7 comments
Closed

Exclude Jpype 1.5.1 #70

hinerm opened this issue Dec 3, 2024 · 7 comments
Assignees
@elevans

Comments

@hinerm
Copy link
Member
hinerm commented Dec 3, 2024

See imagej/napari-imagej#316 and jpype-project/jpype#1242
@ctrueden
Copy link
Member
ctrueden commented Dec 3, 2024

The root cause will need to be fixed upstream in jpype. Doing jpype != 1.5.1 or whatever won't be a good solution if jpype 1.5.2 is released and still has the problem. Based on the discussion in jpype-project/jpype#1242, I do not think anybody has hit upon the actual root cause yet; I doubt it's incomplete JDKs, and someone already chimed in saying the PATH != JAVA_HOME theory is incorrect, too. If someone impacted by the problem is able to debug into the jpype code to see what goes wrong, that would be better.

@ctrueden
Copy link
Member
ctrueden commented Dec 3, 2024

In the meantime: I suggest we do jpype <= 1.5.0 instead, just to be safe.

@elevans
Copy link
Member
elevans commented Dec 3, 2024

Agreed.

elevans added a commit that referenced this issue Dec 3, 2024
@elevans
Limit jpype1 highest version to 1.5.0
a607b5c 
jpype version 1.5.1 fails to start the JVM on Windows for currently
unknown reasons. See #70 and jpype-project/jpype#1242.
@elevans
Copy link
Member
elevans commented Dec 5, 2024

Done a607b5c.

@elevans elevans closed this as completed Dec 5, 2024
@imagesc-bot
Copy link

This issue has been mentioned on Image.sc Forum. There might be relevant details there:

https://forum.image.sc/t/error-during-initialization-of-imagej-in-pyimagej/106008/5

@imagejan
Copy link
Member
imagejan commented Jan 27, 2025 •
edited
Loading

Jpype 1.5.2 was released recently: https://github.com/jpype-project/jpype/releases/tag/v1.5.2

Maybe it's enough to limit to !=1.5.1 now?

@elevans
Copy link
Member
elevans commented Jan 27, 2025

Thanks for the heads up! I'll test jpype 1.5.2, and if all goes well I'll update the requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@elevans elevans

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@ctrueden @hinerm @imagejan @elevans @imagesc-bot
0