Preprocessor/JCP inspired multi-version environment manager
This project was made mainly for my own use within my projects. While stonecutter is not technically "archived", you should not expect much support if you plan on using it.
Instead, consider using KikuGie's fork which greatly expands upon the concept with documentation and additional features.
Here's a link to get you started: https://stonecutter.kikugie.dev/stonecutter/introduction
This gradle/intellij plugin is a manager that allows working on a project that targets multiple compatabile release versions of a dependency. This is mostly meant for Loom-based Fabric projects written in java.
The project is heavily inspired by Preprocessor and JCP and the way they work. While they are great, I had a few issues with them and so this bad boy was made! Huge credit goes to the developers of these projects for giving me the idea!
For the name Stonecutter, I have another gradle plugin named "Fletching Table" and both that plugin and this one are meant to complement Fabric's Loom plugin, you can follow that thinking on your own.
(This project is experimental, use at your own risk and always back up stuff with vcs such as git)
Stonecutter works by taking a gradle project and splitting it into versioned variants of it, adding those subprojects as the parent's children projects. What this does is allow declaring multiple versions of the same project and through the plugin, create multiple versions of the project's code, interweaved using java's comments.
There is the concept of the "active" environment. By convention, inside vcs such as git, it should be the most up-to-date version that the project is targetting and only be switched while working to then be switched back for commits.
When a version is "active", the code for it exists in the source and the child project for it points its sourcesets onto the active environment's src directory. The rest of the code from the other versions is then commented out, as to not interfere with this version's edition of the source.
The main build.gradle script is used by all of the versions and is provided with information about them. Note that this does not stop the different versions from having their own properties files to simplify the setup.
... (section not finished)
Using semver version constraints that are loaded through Fabric Loader's api from the project's dependencies(you can add it to a dummy configuration to pull it if it's not present already), Stonecutter will check and comment out uneeded code for the active version.
... (section not finished)
The project can have a defined set of tokens, based on the concepts of regex replace/substitution and capture groups.
... (section not finished)
Stonecutter is able to set up any task(usually builds or publication tasks), to run concurrently on all versions at once without the need to set the active version for each task.
... (section not finished)
Stonecutter also contains a complementing IDE plugin for Intellij based IDEs. The plugin is meant to ease the usage of Stonecutter but Stonecutter can also work without it.
To install the plugin:
- Open the plugins section in Intellij IDEA(
Ctrl+Alt+S→ Plugins) - Click the gear button at the top
- Click "Install Plugin from Disk..."
- Go to the project folder and open
/.gradle/stonecutter/Stonecutter-<version>.jar(if it's not there, refresh gradle first)
To use the plugin's editor, hit Ctrl+Shift+S while working on a stonecutter project.
... (section not finished)
The way Stonecutter works, is by applying onto the project's settings.gradle to hijack the buildscript locations of the target multiversion project.
Example:
settings.gradle
plugins {
id 'io.shcm.shsupercm.fabric.stonecutter' version '1.3.1'
}
// in this example we'll convert :versionedProject into a multi-versioned "stonecutter" project
include ':versionedProject'
stonecutter.create(project(':versionedProject')) {
// the following definition will add projects ':versionedProject:1.18.2' through to ':versionedProject:1.20'
versions '1.20', '1.19.4', '1.19.2', '1.18.2'
}Refreshing gradle will then create a new script named stonecutter.gradle which is the buildscript of the "controller" of the project.
The versions of the stonecutter project have their directories in the controller project's ./versions/<VERSION>/. Those can have their own gradle.properties and build/run directories.
If you need an example, take a look at the test project for Stonecutter.
Look at the commits for a changelog.
- Make a wiki and actually explaining how to operate Stonecutter
- Intellij Integration: Add easy way of using the tokenizer
- Make the Intellij IDEA plugin easier to install
- Add more integration features to the Intellij IDEA plugin(switch versions, insert versioned code, etc..)
- Proprocessor-style commenting formatter
- Intellij IDEA integration
- Chiseled Tasks
- Regex based token "find and replace" system