[GitHub] [camel-k] squakez commented on pull request #3994: [proposal] Publish a generated extension using jbang and jitpack

2023-01-23 Thread via GitHub
squakez commented on PR #3994: URL: https://github.com/apache/camel-k/pull/3994#issuecomment-1400412044 > This is already the case smile , the jitpack configuration will do a full "release" when you do a GH "Release". I wasn't aware of this feature and it is definetely interesting.

[GitHub] [camel-k] squakez commented on pull request #3994: [proposal] Publish a generated extension using jbang and jitpack

2023-01-23 Thread via GitHub
squakez commented on PR #3994: URL: https://github.com/apache/camel-k/pull/3994#issuecomment-1400107768 Thanks for the explaination. So, this is not really going to replace the dependency in a repo, but instead would create one on demand when it's requested by the user. I'm not totally agai

[GitHub] [camel-k] squakez commented on pull request #3994: [proposal] Publish a generated extension using jbang and jitpack

2023-01-20 Thread GitBox
squakez commented on PR #3994: URL: https://github.com/apache/camel-k/pull/3994#issuecomment-1398454905 What I still miss to understand who is going to consume such new configurations and how the jar will end up into `com.github.andreaTP:camel-k:0.0.2-SNAPSHOT`. I suppose you have some proc

[GitHub] [camel-k] squakez commented on pull request #3994: [proposal] Publish a generated extension using jbang and jitpack

2023-01-20 Thread GitBox
squakez commented on PR #3994: URL: https://github.com/apache/camel-k/pull/3994#issuecomment-1398091804 Thanks for submitting the PR. However I am not able to entirely understand how this is going to work. Is it some user that need to run some command with the proposed configuration? Can yo