You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/07/22 09:30:40 UTC

[GitHub] [camel-k] squakez commented on pull request #2516: Add classpath kamelet loading test

squakez commented on pull request #2516:
URL: https://github.com/apache/camel-k/pull/2516#issuecomment-884776989


   > > I have some concern.
   > > I am not sure if we should rely on external kamelet provider, altough it's the official kamelet catalog. I'd prefer to create a copy of the Kamelet we want to test locally instead.
   > 
   > I am not sure how to make it. The copy of the Kamelet has to be packaged to a maven repository and I didn't find a way how to force jitpack to work with repository subdirs. Can you advise me in this area?
   > 
   
   I think you can provide it as a custom resource. I guess you can leverage the same API and maybe provide some support method to use that also in the future.
   
   > > For sure, we should not use a Kamelet that is polling an external service. If the external service is broken, our CI will break as well.
   > 
   > Yes, you are right I will fix it.
   
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org