Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

have a jbang resolve or jbang export than just fetch dependencies #1730

Open
maxandersen opened this issue Jan 13, 2024 · 1 comment
Open
Labels
ideas Some idea/suggestion around jbang behavior/feature set

Comments

@maxandersen
Copy link
Collaborator

usecase is to allow use jbang resolution together with existing toolchains.

i.e. today jbang export portable <scriptref> assumes there always is a scriptref to start with.

what if you could do jbang export libs --deps g:a:v,g:a:v and a libs folder will be created with the content in there.

not sure if we want new command or just allow existing export commands work without a scriptref trigger it work as a resolve only.

recent discussion: https://www.reddit.com/r/java/comments/194o1wh/the_java_command_line_workflow/

@maxandersen maxandersen added the ideas Some idea/suggestion around jbang behavior/feature set label Jan 13, 2024
@quintesse
Copy link
Contributor

This is obviously very useful functionality and we should definitely add this.

Soapbox: but to me it's also an example of what we discussed earlier in one of our chats, that JBang in my opinion is getting a bit big, with useful features like this somewhat "pushed down" and added to sub(sub) commands that are not part of its main functionality. This makes them less accessible, and therefore less useful, when they could/should be a central part of making "Living with Java" easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ideas Some idea/suggestion around jbang behavior/feature set
Projects
None yet
Development

No branches or pull requests

2 participants