diff --git a/templates/architectury/build.gradle b/templates/architectury/build.gradle index c810525..5cb6e62 100644 --- a/templates/architectury/build.gradle +++ b/templates/architectury/build.gradle @@ -1,6 +1,6 @@ plugins { id "architectury-plugin" version "3.4-SNAPSHOT" - id "dev.architectury.loom" version "0.12.0-SNAPSHOT" apply false + id "dev.architectury.loom" version "1.1-SNAPSHOT" apply false } architectury { diff --git a/templates/forge/build.gradle b/templates/forge/build.gradle index 856bdb5..c72a7eb 100644 --- a/templates/forge/build.gradle +++ b/templates/forge/build.gradle @@ -1,5 +1,5 @@ plugins { - id "dev.architectury.loom" version "0.12.0-SNAPSHOT" + id "dev.architectury.loom" version "1.1-SNAPSHOT" id "maven-publish" } @@ -32,24 +32,6 @@ loom { // also, any names used in your access transformer will need to be // in SRG mapped ("func_" / "field_" with MCP class names) to work! // (both of these things may be subject to change in the future) - - // this will create a data generator configuration - // that you can use to automatically generate assets and data - // using architectury loom. Note that this currently *only* works - // for forge projects made with architectury loom! - dataGen { - mod project.mod_id - } - } - - // This allows you to modify your launch configurations, - // for example to add custom arguments. In this case, we want - // the data generator to check our resources directory for - // existing files. (see Forge's ExistingFileHelper for more info) - launches { - data { - arg "--existing", file("src/main/resources").absolutePath - } } } @@ -139,13 +121,7 @@ jar { publishing { publications { mavenJava(MavenPublication) { - // add all the jars that should be included when publishing to maven - artifact(remapJar) { - builtBy remapJar - } - artifact(sourcesJar) { - builtBy remapSourcesJar - } + from components.java } }