Skip to content
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

11.0.0-SNAPSHOT apiVersion uses 1.20 instead of 1.20.1 for spongeRuntime #70

Open
jpenilla opened this issue Aug 4, 2023 · 2 comments · May be fixed by #82
Open

11.0.0-SNAPSHOT apiVersion uses 1.20 instead of 1.20.1 for spongeRuntime #70

jpenilla opened this issue Aug 4, 2023 · 2 comments · May be fixed by #82

Comments

@jpenilla
Copy link
Contributor

jpenilla commented Aug 4, 2023

The + version from SpongePluginGradle#addRuntimeDependency is selecting 1.20 over 1.20.1, it's also in the wrong order on the Nexus web ui

Screenshot

As a workaround I forced the version with

configurations.spongeRuntime {
    resolutionStrategy {
        eachDependency {
            if (target.name == "spongevanilla") {
                useVersion("1.20.1-11.0.0-RC1356")
            }
        }
    }
}
@jpenilla
Copy link
Contributor Author

jpenilla commented Aug 4, 2023

1.20.+ also seems to work for the version override workaround

@jpenilla jpenilla changed the title 11.0.0-SNAPSHOT uses 1.20 instead of 1.20.1 for spongeRuntime 11.0.0-SNAPSHOT apiVersion uses 1.20 instead of 1.20.1 for spongeRuntime Aug 4, 2023
@jpenilla jpenilla linked a pull request Feb 21, 2024 that will close this issue
Draft
@gabizou
Copy link
Member

gabizou commented Jan 27, 2025

To note, this also happens with API 13 (per user report)

If you use the workaround from here to specify an exact build like "1.21.3-13.0.1-RC2025", it complains that "no matching variant is found"
No matching variant of org.spongepowered:spongevanilla:1.21.3-13.0.1-RC2025 was found. The consumer was configured to find attribute 'org.spongepowered.api-target' with value '13.0.0'

I'm not at all sure how to handle it explicitly, without being able to add a version tag that you can further specify the MC version in the dependency somehow, because that is definitely doable

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

Successfully merging a pull request may close this issue.

Use sponge downloads API to select latest vanilla runtime for API version jpenilla/SpongeGradle
2 participants
@gabizou @jpenilla