Mirror/MarginaliaSearch
1
0
Fork 0
mirror of https://github.com/MarginaliaSearch/MarginaliaSearch.git synced 2025-02-24 21:29:00 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
59ec70eb73
MarginaliaSearch/code/common/config/build.gradle

38 lines
925 B
Groovy
Raw Normal View History

Restructuring the git repo
2023-03-04 12:19:01 +00:00
plugins {
id 'java'
(*) Upgrade to JDK21 with preview enabled. ... also move some common configuration into the root build.gradle-file. Support for JDK21 in lombok is a bit sketchy at the moment, but it seems to work. This upgrade is kind of important as the new index construction really benefits from Arena based lifecycle control over off-heap memory.
2023-09-23 09:01:43 +00:00
Restructuring the git repo
2023-03-04 12:19:01 +00:00
id 'jvm-test-suite'
}
java {
toolchain {
(build) Java 22 and its consequences has been a disaster for Marginalia Search Roll back to JDK 21 for now, and make Java version configurable in the root build.gradle The project has run into no less than three distinct show-stopping bugs in JDK22, across multiple vendors, and gradle still doesn't fully support it, meaning you need multiple JDK versions installed.
2024-04-24 11:54:04 +00:00
languageVersion.set(JavaLanguageVersion.of(rootProject.ext.jvmVersion))
Restructuring the git repo
2023-03-04 12:19:01 +00:00
}
}
(refac) Remove src/main from all source code paths. Look, this will make the git history look funny, but trimming unnecessary depth from the source tree is a very necessary sanity-preserving measure when dealing with a super-modularized codebase like this one. While it makes the project configuration a bit less conventional, it will save you several clicks every time you jump between modules. Which you'll do a lot, because it's *modul*ar. The src/main/java convention makes a lot of sense for a non-modular project though. This ain't that.
2024-02-23 15:13:40 +00:00
apply from: "$rootProject.projectDir/srcsets.gradle"
Restructuring the git repo
2023-03-04 12:19:01 +00:00
dependencies {
(*) WIP Control GUI redesign, executor-service, multi-node mq This turned out to be very difficult to do in small isolated steps. * Design overhaul of the control gui using bootstrap * Move the actors out of control-service into to a new executor-service, that can be run on multiple nodes * Add node-affinity to message queue
2023-10-14 10:07:40 +00:00
implementation project(':code:common:db')
implementation project(':code:common:model')
implementation libs.bundles.slf4j
implementation libs.bundles.mariadb
implementation libs.mockito
implementation libs.guice
implementation libs.gson
testImplementation libs.bundles.slf4j.test
testImplementation libs.bundles.junit
(test) Clean up test usage of migrations Several tests were manually running migrations in a large copy-paste blob of code. This makes the test less useful as it's possible to break the code while keeping the tests green by introducing a new migration that never gets run in the tests, and it's also difficult to reason about what the tests are doing. A new test helper library is introduced with a TestMigrationLoader that can both run Flyway migrations, or load specific migrations in the cases a specific set of migrations need to be loaded. Existing tests are migrated to use the new code.
2024-01-12 14:55:50 +00:00
testImplementation project(':code:libraries:test-helpers')
(*) WIP Control GUI redesign, executor-service, multi-node mq This turned out to be very difficult to do in small isolated steps. * Design overhaul of the control gui using bootstrap * Move the actors out of control-service into to a new executor-service, that can be run on multiple nodes * Add node-affinity to message queue
2023-10-14 10:07:40 +00:00
testImplementation platform('org.testcontainers:testcontainers-bom:1.17.4')
testImplementation 'org.testcontainers:mariadb:1.17.4'
testImplementation 'org.testcontainers:junit-jupiter:1.17.4'
(test) Clean up test usage of migrations Several tests were manually running migrations in a large copy-paste blob of code. This makes the test less useful as it's possible to break the code while keeping the tests green by introducing a new migration that never gets run in the tests, and it's also difficult to reason about what the tests are doing. A new test helper library is introduced with a TestMigrationLoader that can both run Flyway migrations, or load specific migrations in the cases a specific set of migrations need to be loaded. Existing tests are migrated to use the new code.
2024-01-12 14:55:50 +00:00
testImplementation project(':code:libraries:test-helpers')
(*) WIP Control GUI redesign, executor-service, multi-node mq This turned out to be very difficult to do in small isolated steps. * Design overhaul of the control gui using bootstrap * Move the actors out of control-service into to a new executor-service, that can be run on multiple nodes * Add node-affinity to message queue
2023-10-14 10:07:40 +00:00
Restructuring the git repo
2023-03-04 12:19:01 +00:00
}
Reference in New Issue Copy Permalink