Replies: 3 comments 12 replies
-
The --verbose flag has to be put before the filename, anything after the filename is considered arguments for the application. |
Beta Was this translation helpful? Give feedback.
-
You are not pointing to a quarkus app jar afaics. You are pointing to a jar with lots of quarkus Dev deps. Not sure what to suggest as not sure what app you have but as long as the pom says it has those deps jbang Will honor that. And as we don't have exclude option yet it will cosntinue happen. Possible solutions as of today is to point to a Uber jar or make a pom.xml with the true dependencies. |
Beta Was this translation helpful? Give feedback.
-
kind of. not sure what we can do to fix it as its really a maven limiitation. |
Beta Was this translation helpful? Give feedback.
-
We have a Quarkus multi module build where one module is:
It makes sense for us to build those together since they share some logic/code.
When we publish the client-SDK jar, it has a lot of dependencies. Extract of a
mvn org.apache.maven.plugins:maven-dependency-plugin:3.6.1:tree
command:Point 1) probably we can improve the publication process of our library. It is probably wrong that this one is based on quarkus. This is probably a "dependency leak", due to the current project setup.
Point 2) right now when we start a small jbang script that is using this single library, it doesn't work. We get:
The
--verbose
flag does not help.Any idea how I can prevent the
JBangIntegration
step to be executed (I think it is inquarkus-ide-launcher
) ?My guess is that I am not interested at all by the quarkus tooling for this jar, since this is not a quarkus app.
Or what can I do to investigate what is going on?
If there is some interest, I could try to share a reproducer.
Maybe the problem is more in the quarkus project setup than in Jbang itself...
Beta Was this translation helpful? Give feedback.
All reactions