ppalaga commented on issue #2045: URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-744372751
Yes, creating a Camel Quarkus app is very Maven-repo centric. Whether in Maven or in Gradle based apps, the parts of the application are declared in terms of Maven artifact coordinates and the Quarkus toolling uses given tool's resolution mechanisms to get those parts. Note that its impossible to assemble a Camel Quarkus app without Quarkus build Mojo (or the corresponding Gradle task), because that's where the Augmentation (build time analysis and transformation of the application code) is happening. So there is no way how a user could "put together" an app by moving around jars we give him in a zip file. Unless of course, he installs the jars into his local Maven repo. Zipped Maven repo is actually a perfect match for the Quarkus process, even in offline environments: it can be unzipped locally and declared as an additional repo in the application's build.gradle, pom.xml or in settings.xml. In that way, the Quarkus tooling can find the necessary artifacts where it expects them. Having said that I would not mind having a look how we could provide a zipped maven repo containing our binary jars and nothing else. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
