java-commons/settings.gradle.kts

rootProject.name = "JfCommons"

include("commons")
include("commons-io")
include("commons-http-client")
include("commons-http-server")
// serialization
include("commons-serialize")
include("commons-serialize-dsl")
include("commons-serialize-json")
include("commons-serialize-xml")
include("commons-serialize-databind")
include("commons-serialize-databind-api")
include("commons-serialize-databind-sql")
// new muscript
include("muscript-core")
include("muscript-ast")
include("muscript-data-dynamic")
include("muscript-data-additional")
include("muscript-parser")
include("muscript-serialize")
include("muscript-optimizer")
include("muscript-runtime")
include("muscript-json")
// interop
include("commons-logger")
include("commons-manifold")
include("commons-gson")
include("commons-unsafe")

enableFeaturePreview("TYPESAFE_PROJECT_ACCESSORS")
feat: replace commons-logging with slf4j-based commons-logger and use type-safe dependency DSLs The only reason it needed to be separate was logging during ultra early init in Minecraft. I can figure out something else for that. 2024-03-09 12:37:38 +01:00			`rootProject.name = "JfCommons"`
[root] Use gradle kotlin dsl 2022-11-01 18:55:17 +01:00
build: move core commons to submodule to clean up build 2023-09-21 19:08:14 +02:00			`include("commons")`
feat(serialize-databind): split into databind and databind-api 2024-04-13 13:48:34 +02:00			`include("commons-io")`
			`include("commons-http-client")`
			`include("commons-http-server")`
			`// serialization`
BREAKING: modularize 2023-09-21 21:08:40 +02:00			`include("commons-serialize")`
feat(serialize-dsl): port serialize-gson-dsl to commons-serialization 2024-04-13 14:21:28 +02:00			`include("commons-serialize-dsl")`
feat(serialize): implement data binding 2024-04-12 19:35:00 +02:00			`include("commons-serialize-json")`
feat(serialize-xml): initial prototyping for xml reader 2024-04-13 19:23:31 +02:00			`include("commons-serialize-xml")`
feat(serialize): implement data binding 2024-04-12 19:35:00 +02:00			`include("commons-serialize-databind")`
feat(serialize-databind): split into databind and databind-api 2024-04-13 13:48:34 +02:00			`include("commons-serialize-databind-api")`
feat(serialize): implement data binding 2024-04-12 19:35:00 +02:00			`include("commons-serialize-databind-sql")`
feat: initial port of muscript ast to ADT-based module 2024-04-03 18:30:24 +02:00			`// new muscript`
feat(muscript): implement serialization 2024-04-05 14:21:17 +02:00			`include("muscript-core")`
feat: initial port of muscript ast to ADT-based module 2024-04-03 18:30:24 +02:00			`include("muscript-ast")`
feat(muscript): implement serialization 2024-04-05 14:21:17 +02:00			`include("muscript-data-dynamic")`
			`include("muscript-data-additional")`
			`include("muscript-parser")`
			`include("muscript-serialize")`
feat(muscript): initial implementation of muscript-optimizer 2024-04-05 17:58:26 +02:00			`include("muscript-optimizer")`
feat(muscript): implement muscript-runtime 2024-04-07 15:36:33 +02:00			`include("muscript-runtime")`
feat(muscript-gson): rename to muscript-json and port to commons-serialize-json 2024-04-12 21:19:36 +02:00			`include("muscript-json")`
feat(serialize-databind): split into databind and databind-api 2024-04-13 13:48:34 +02:00			`// interop`
			`include("commons-logger")`
			`include("commons-manifold")`
			`include("commons-gson")`
			`include("commons-unsafe")`
feat: replace commons-logging with slf4j-based commons-logger and use type-safe dependency DSLs The only reason it needed to be separate was logging during ultra early init in Minecraft. I can figure out something else for that. 2024-03-09 12:37:38 +01:00
			`enableFeaturePreview("TYPESAFE_PROJECT_ACCESSORS")`