* Improve locking strategy for concurrent loom executions
This is especially useful for when IntelliJ decides to randomly sync the
Gradle project while I am running Gradle from the command line already.
* Fix style violations
* Adjust feedback messages and use Duration for timeout
* Fixup message
* Prepare for SelfResolvingDependency's removal
Update to Gradle 8.6
* Update docker images
* ProjectDependency is also a SRD
* Throw if layered mappings are created too late.
We have to read every jar on remapped configs to see if they are a mod or should otherwise be remapped. By caching we can avoid re-reading jars that are java-runtime & java-api or are on multiple remapped configs. The cache scope could probably be widened to help more with multi-project builds, but I am leaving that for future work as I think it would also require some sort of invalidation.
* Only mixin remap/analyse classpath jars that use static mixin remappings.
* More of a mess
* Less of a mess?
* Nope?
* Exclude the none root MC jars from the remap classpath when using MPO
* Improve test a little
* Update TR
* Checkstyle
* Fix DLN test
* Fix possible crash when closing build services
No longer processes the jar multiple times, caches the jar in place.
ZipReprocessorUtil now directly writes the file to disk, instead of first copying it to memory.
* Fix data gen folder not being added to resources.
Closes https://github.com/FabricMC/fabricmc.net/issues/69
* Allow disabling RunConfig appending project path
Add a `appendConfigNameWithPath` property to `RunConfigSettings` controlling whether to append the path for non-root projects.
Default behaviour is unchanged.
---------
Co-authored-by: modmuss50 <modmuss50@gmail.com>
* Change how `include` disables transitive dependencies to allow platform dependencies to work
* style fix
* Cleanup and add test
* spotlessApply
---------
Co-authored-by: modmuss50 <modmuss50@gmail.com>
* Skip remapping in `AbstractRemapJarTask`s when source and target namespaces match
The "remap jar" tasks have much more functionality than simply remapping jars at this point, such as adding namespace metadata, nesting jars, ensuring reproducible builds, etc. Some custom build logic may want to take advantage of these features without the full overhead of no-op remapping with TinyRemapper/Mercury.
* Add test
* Support mixins without refmaps in mod dependencies
* Fix review concerns
* Add test for MixinDetector
* Change warning to a RuntimeException
* FabricAPITest: Test building without mixin AP
* Deal with Eclipse being stuck in the 2010s and not supporting basic Groovy syntax
* Auto-fix Groovy code format
* Fix FabricAPITest not running
* Fix code style
* Add fabricApi.configureDataGeneration API/DSL to help with setting up datageneration.
* Clean + add option to not add to resources
* Dont create new task
