Put the client extra artifact on the classpath (#29)

So IJ can find it
neoforged · Jun 16, 2024 · ae4f8ae · ae4f8ae
1 parent a7f059a
commit ae4f8ae
Showing 1 changed file with 1 addition and 7 deletions.
diff --git a/src/main/java/net/neoforged/moddevgradle/internal/ModDevPlugin.java b/src/main/java/net/neoforged/moddevgradle/internal/ModDevPlugin.java
@@ -236,13 +236,7 @@ public void apply(Project project) {
             config.setCanBeConsumed(false);
             config.withDependencies(dependencies -> {
                 dependencies.addLater(minecraftClassesArtifact.map(dependencyFactory::create));
-                // In Vanilla-Mode, we have to add the Vanilla resources too since the legacy
-                // classpath (where they normally are) is ignored
-                dependencies.addLater(project.getProviders().zip(
-                        createArtifacts.map(task -> project.files(task.getResourcesArtifact())),
-                        hasNeoForge,
-                        (resources, hasNeoForgeValue) -> !hasNeoForgeValue ? dependencyFactory.create(resources) : null
-                ));
+                dependencies.addLater(createArtifacts.map(task -> project.files(task.getResourcesArtifact())).map(dependencyFactory::create));
 
                 // Technically the Minecraft dependencies do not strictly need to be on the classpath because they are pulled from the legacy class path.
                 // However, we do it anyway because this matches production environments, and allows launch proxies such as DevLogin to use Minecraft's libraries.