The Nitto buildsystem - written in java

Go to file

Mai Lapyst bc158e076f bithero_agency/nitto/nitto-java/pipeline/head This commit looks good Details Add clang toolchain		2023-11-27 00:16:50 +01:00
.vscode	Some updates (git, maven, java/c++, gnu autotools)	2021-06-19 06:44:59 +02:00
dev_scripts	dev_scripts/nitto-dev now uses the version in pom.xml to find the correct jarfile	2023-03-18 06:07:18 +01:00
docs	Added "java sealpkg" to add sealed packages to the manifest	2023-01-30 20:15:49 +01:00
resources/mai_lapyst/nitto/res/toolchains	Add clang toolchain	2023-11-27 00:16:50 +01:00
src	Set sys.outDir and sys.buildDir to absolute paths	2023-10-28 16:35:10 +02:00
test	Expand c++ test to account for dependencies of dependencies	2023-04-12 10:19:17 +02:00
.gitignore	Update .gitignore	2023-10-27 15:00:06 +02:00
Jenkinsfile	Fix jenkinsfile for release build	2023-03-16 14:07:52 +01:00
LICENSE	Initial Commit	2021-05-08 22:27:58 +02:00
README.MD	Initial Commit	2021-05-08 22:27:58 +02:00
pom.xml	Prepare for next development cycle	2023-04-15 13:43:05 +02:00
run.sh	Initial Commit	2021-05-08 22:27:58 +02:00
test.rb	Updates:	2021-07-24 07:08:14 +02:00
test.sh	Some updates (git, maven, java/c++, gnu autotools)	2021-06-19 06:44:59 +02:00

README.MD

Nitto

Nitto (japanse for 'knit'), is an declarative buildsystem with plugin support. Currently written in java and compatible with graalvm.

Building

Currently Nitto is only builded by a minimalistic maven file.

To build it (as ready to use jar) execute:

mvn package

To run it outside the source installation, simply execute ./run.sh with any nitto arguments.

Tests

Nitto comes with some "test-projects" which are both tests and examples. To run these from an development installation just use the ./test.sh helper script.

The first argument must be the test postfix, for example to run the test/test_java project:

./test.sh java

After that can come any nitto arguments, because the script just executes the development nitto instance inside the correct workingdirectory.