refactor: introduced jbang-core
library
#1128
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just to start up the discussion on how to go about creating a jbang library that people could use to create plugins or tools or in any other way interact with Jbang.
Right now I simply hacked the project in two: where almost all
cli
code remains in the current top-level project and all the rest was moved to a newjbang-core
sub project.It doesn't currently compile because I'm not very well-versed with Gradle, but it's 90% there I'm sure.
Also, the code hasn't been restructured in any way which means we're actually "overlaying" packages (
dev.jbang.cli
exists in both projects for example) which might cause problems, especially when Java's module system gets more and more strict.Anyway, doing it like this was about an hour's work, which means it won't be that hard to re-do this PR if/when we actually decide to go ahead with this.