sander/jargo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

expanded a README

Browse source
This commit is contained in:
Shautvast 2024-01-15 14:08:09 +01:00
parent 55020dc097
commit 1b86321b69
1 changed files with 24 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
README.md
View file

@ -1,3 +1,5 @@
**Jargo**
Exploring the need/possibility to move from maven/gradle to cargo.
That is, build tool for java taking inspiration from Cargo
@ -8,12 +10,15 @@ but 'jargo' actually sounds kinda nice and it conveys pretty much what it is.
It is NOT a new maven (not yet at least).
Basic premisses:
1. do NOT copy anything from the maven philosophy (phases, goals etc). Instead find out on the go what would be
1. written in Rust
2. does NOT copy anything from the maven philosophy (phases, goals etc). Instead find out on the go what would be
a good design
2. uses TOML
3. uses TOML
see [tests/sample_project/Jargo.toml]() to get an impression of what that looks like.
Goals:
1. Simple management of (test) dependencies
1. Simple management of (test) dependencies, using existing maven repositories
2. ability to compile to jar files
3. ability to run unit tests
@ -21,3 +26,19 @@ After this, we'll validate it's performance. If it's not faster/easier/better th
But instead, if it will save you time/resources/heart failure, then why not take this next level?
4. upload to maven repo's
5. plugin mechanism for specific goals (code generation, javadoc, etc).
6. migrating from maven in actual projects
Questions:
1. Why?
_Every tool is currently being rewritten in rust._ And for good reason!
2. Why not create a drop-in replacement for maven written in rust?
_While that would make migration a no-brainer, it seems too ambitious based on what I've seen of the maven
codebase_