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

option for turning on/off integrations #1776

Open
maxandersen opened this issue Mar 22, 2024 · 3 comments
Open

option for turning on/off integrations #1776

maxandersen opened this issue Mar 22, 2024 · 3 comments
Labels
ideas Some idea/suggestion around jbang behavior/feature set

Comments

@maxandersen
Copy link
Collaborator

as discussed in #1774 there can be situatons where the classpath contains integrations you dont want to run.

we should at a minimum have a global off switch, maybe --no-integrations where --integrations are default ?

possibly consider --integrations=none and --integrations=all is default and open up for allowing list of '.' names to turn on/off specific integrations?

@maxandersen maxandersen added the ideas Some idea/suggestion around jbang behavior/feature set label Mar 22, 2024
@jmini
Copy link
Contributor

jmini commented Mar 22, 2024

Couldn't it be something that is controlled in the comments of the file itself? Similar to other keywords like: //DEPS, //REPOS, //JAVA.

I would prefer having it in the source than having to type it on the command line every time I execute the script.

@quintesse
Copy link
Contributor

@maxandersen perhaps this should be part of the build steps feature I had been working on some time ago? There were several ways to select which steps to run, including from the sleeve file. We could then great the quarkus integration as a kind of legacy build step.

@maxandersen
Copy link
Collaborator Author

How would that look?

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

3 participants