* Initial 1.17 configuration, dep upgrade.
* Enable 1.18 for initial tests.
* Add lowcodelanguage for 1.18 (#49)
* Set classpath flag for 1.17+ generated files. Enable 1.19 (not yet working).
* Support 1.19.
Co-authored-by: Matt Artist <me@mja00.dev>
CHANGES
- Forge installer is no longer stored to the work directory. It is now stored in a cache folder corresponding to the artifact version.
- Installer output is now cached by default
- Added options to generate distro.
- --discardOutput Delete cached output after it is no longer required. May be useful if disk space is limited.
- --invalidateCache Invalidate and delete existing caches as they are encountered. Requires fresh cache generation.
- Both options are false by default.
- To invalide a single version, manually delete the folder.
- Old functionality is essentially g distro --discardOutput --invalidateCache.
JSON schemas are used by editors to validate data and provide useful insights.
The JSON schemas will be generated by the init root command. They can also be generated
using the generate schemas command.
The JSON files will reference the schemas on the user's local disk rather than hosted versions.
This allows offline editing and ensures that the schema is exactly one-to-one with the local
version of Nebula.
Existing servers will have to manually add the schema property. To see how to do this, generate
a new server and copy the $\schema value.
The schema property will need to be added to any existing distrometa files. This is the same
format as the server meta, just replace ServerMeta with DistroMeta.
More information, including sample files with json schemas, is provided
on the README.
