Instead of relying on a global placeholder, bake the version into the neoforge.mods.toml

[shartte]

Currently, it's not possible to get the version of NeoForge simply based on the jar file itself, since it sets its own version to whatever was passed on the CLI commandline.

This PR changes that by replacing the placeholder with the actual project version number, when NF is built.

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: ccb2af05e927933d23e557d634557db200f06646.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged:neoforge:21.0.45-beta-pr-1207-bake-version-into-neoforge-mods-toml
• 📦 net.neoforged:testframework:21.0.45-beta-pr-1207-bake-version-into-neoforge-mods-toml

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 #1207' // https://github.com/neoforged/NeoForge/pull/1207
        url 'https://prmaven.neoforged.net/NeoForge/pr1207'
        content {
            includeModule('net.neoforged', 'neoforge')
            includeModule('net.neoforged', 'testframework')
        }
    }
}

MDK installation

In order to setup a MDK using the latest PR version, run the following commands in a terminal.
The script works on both *nix and Windows as long as you have the JDK bin folder on the path.
The script will clone the MDK in a folder named NeoForge-pr1207.
On Powershell you will need to remove the -L flag from the curl invocation.

mkdir NeoForge-pr1207
cd NeoForge-pr1207
curl -L https://prmaven.neoforged.net/NeoForge/pr1207/net/neoforged/neoforge/21.0.45-beta-pr-1207-bake-version-into-neoforge-mods-toml/mdk-pr1207.zip -o mdk.zip
jar xf mdk.zip
rm mdk.zip || del mdk.zip

To test a production environment, you can download the installer from here.