Jar-in-Jar: Throw when only incompatible version ranges were specified

[shartte]

For example, Gradle allows [1.0,2.0[, but Maven insists on [1.0,2.0).

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: 7a93e007d9298c5bc7bdc22c611ff10f28121d02.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged.moddev.repositories:net.neoforged.moddev.repositories.gradle.plugin:0.1.99-pr-30-validate-version-ranges
• 📦 net.neoforged.moddev:net.neoforged.moddev.gradle.plugin:0.1.99-pr-30-validate-version-ranges
• 📦 net.neoforged:moddev-gradle:0.1.99-pr-30-validate-version-ranges

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 #30' // https://github.com/neoforged/ModDevGradle/pull/30
        url 'https://prmaven.neoforged.net/ModDevGradle/pr30'
        content {
            includeModule('net.neoforged.moddev.repositories', 'net.neoforged.moddev.repositories.gradle.plugin')
            includeModule('net.neoforged.moddev', 'net.neoforged.moddev.gradle.plugin')
            includeModule('net.neoforged', 'moddev-gradle')
        }
    }
}

[Technici4n]

Shouldn't we throw if any version range is invalid?

[shartte]

Shouldn't we throw if any version range is invalid?

IDK, it would certainly make the coder easier...