Add support for locating mod sources with services from the classpath.

[marchermans]

This allows a SERVICE-layer source set or jar to be loaded from the classpath in userdev if it is part of the MOD_CLASSES.

[FiniteReality]

This change seems fine as-is. Maybe we should consider extracting the parsing of MOD_CLASSES to a common location - I believe there's an exact duplicate of this logic in MinecraftLocator as well as one or two other places.

[FiniteReality]

Now that we're delegating to this method, is shouldLoadInServiceLayer a good name for this method? Would something like isValidServiceLayerJar be a better name?

(I would have put this comment on the declaration of the method a few lines above, but it wasn't changed so I couldn't)

[Technici4n]

I think it's fine like this. Find a synonymous name doesn't make the method clearer.

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: 8e92bdc964368f4cf771d9a44099929d071bc910.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged.fancymodloader:spi:2.0.28-pr-93-feature-service-layer-classpath-discovery
• 📦 net.neoforged.fancymodloader:earlydisplay:2.0.28-pr-93-feature-service-layer-classpath-discovery
• 📦 net.neoforged.fancymodloader:loader:2.0.28-pr-93-feature-service-layer-classpath-discovery

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 #93' // https://github.com/neoforged/FancyModLoader/pull/93
        url 'https://prmaven.neoforged.net/FancyModLoader/pr93'
        content {
            includeModule('net.neoforged.fancymodloader', 'spi')
            includeModule('net.neoforged.fancymodloader', 'earlydisplay')
            includeModule('net.neoforged.fancymodloader', 'loader')
        }
    }
}