Skip to content

Conversation

@shartte
Copy link
Contributor

@shartte shartte commented Jan 2, 2025

  1. It will first try to find the dynamic version in the artifact manifest
  2. If that fails, it gathers all available versions from across all repositories (uncached) and then substitutes the best matching version

@neoforged-pr-publishing
Copy link

neoforged-pr-publishing bot commented Jan 2, 2025

  • Publish PR to GitHub Packages

Last commit published: f3e31be2b5791d4366ea37ca29f059b5dfff0cb8.

PR Publishing

The artifacts published by this PR:

Repository Declaration

In order to use the artifacts published by the PR, add the following repository to your buildscript:

repositories {
    maven {
        name 'Maven for PR #55' // https://github.com/neoforged/NeoFormRuntime/pull/55
        url 'https://prmaven.neoforged.net/NeoFormRuntime/pr55'
        content {
            includeModule('net.neoforged', 'neoform-runtime')
        }
    }
}


// Special case: NeoForge reference libraries that are only available via the Mojang download server
if (mavenCoordinate.groupId().equals("com.mojang") && mavenCoordinate.artifactId().equals("logging")) {
if (mavenCoordinate.groupId().equals("com.mojang") && mavenCoordinate.artifactId().equals("logging")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm being pedantic but I would surround the ands in their own parenthesis for clarity's sake

// See if it's a dynamic version and match against all entries
if (artifactCoordinate.isDynamicVersion()) {
for (var entry : externallyProvided.entrySet()) {
if (artifactCoordinate.matchesVersion(entry.getKey().version())
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this check should be matches artifact first and version second

@neoforged-automation neoforged-automation bot added the needs rebase This Pull Request needs to be rebased before being merged label Jun 14, 2025
@neoforged-automation
Copy link

@shartte, this pull request has conflicts, please resolve them for this PR to move forward.

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

Labels

needs rebase This Pull Request needs to be rebased before being merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants