nitto/nitto-java
1
0
Fork 0
Code Issues Pull requests Projects Releases 3 Packages Wiki Activity Actions
The Nitto buildsystem - java version
621 commits 1 branch 3 tags 1.6 MiB
  • Java 98.8%
  • Shell 0.5%
  • Ruby 0.4%
  • C++ 0.2%
  • M4 0.1%
Find a file
Exact
Mai-Lapyst 978e7902f4
All checks were successful
/ build (push) Successful in 45s
Details
Java: make java parsing more relaxed
2026-05-04 02:58:16 +02:00
.forgejo/workflows workflow: fix maven download location 2026-04-24 14:57:40 +02:00
.vscode Some updates (git, maven, java/c++, gnu autotools) 2021-06-19 06:44:59 +02:00
dev_scripts Fix argument passing in dev scripts 2024-12-20 10:32:55 +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 License: Add header checking 2026-03-12 13:50:32 +01:00
src Java: make java parsing more relaxed 2026-05-04 02:58:16 +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
LICENSE Initial Commit 2021-05-08 22:27:58 +02:00
pom.xml dep: update javaparser 2026-04-24 09:14:00 +02:00
README.MD Initial Commit 2021-05-08 22:27:58 +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.