8000 BoneJ v7.1.1 by mdoube · Pull Request #291 · scijava/pom-scijava · GitHub
[go: up one dir, main page]
Skip to content

BoneJ v7.1.1 #291

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
Merged
merged 1 commit into from
May 28, 2025
Merged

BoneJ v7.1.1 #291

merged 1 commit into from
May 28, 2025

Conversation

mdoube
Copy link
Contributor
@mdoube mdoube commented May 9, 2025

Updates BoneJ to 7.1.1, which includes the new bonej-plus package for GPU accelerated processing

@ctrueden ctrueden merged commit 260925d into scijava:master May 28, 2025
@ctrueden
Copy link
Member

Belated thanks, @mdoube !

@ctrueden
Copy link
Member
ctrueden commented Jun 3, 2025 •
edited
Loading

@mdoube There is a problem with bonej-plus:

Could not resolve dependencies for project org.scijava:mega-melt:pom:0-SNAPSHOT: Failed to collect dependencies at org.bonej:bonej-plugins:jar:7.1.1 -> org.bonej:bonej-plus:jar:0.0.4: Failed to read artifact descriptor for org.bonej:bonej-plus:jar:0.0.4: Could not transfer artifact org.bonej:bonej-plus:pom:0.0.4 from/to github (https://maven.pkg.github.com/bonej-org/bonej-plus): authentication failed for https://maven.pkg.github.com/bonej-org/bonej-plus/org/bonej/bonej-plus/0.0.4/bonej-plus-0.0.4.pom, status: 401 Unauthorized

Could you please stop using this extra repository, in favor of using maven.scijava.org like we do for everything else?

Or minimally: make it public? But if you decide to keep using it, understand that it imposes another point of failure on all projects that depend on bonej.

@mdoube
Copy link
Contributor Author
mdoube commented Jun 4, 2025

@ctrueden sorry about this. Will look into how to publish the artefact somewhere everyone can get it. bonej-org has the maven.scijava.org tokens so maybe I can tweak the Actions / pom.xml to deploy there rather than / as well as GitHub packages. In the meantime if this breaks things for scijava, probably best to roll back this PR until I've got a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@mdoube @ctrueden
0