[GitHub] [camel-karavan] davsclaus commented on issue #749: Allow user to upload a jar file.

["davsclaus (via GitHub)" <gi...@apache.org>]

davsclaus commented on issue #749:
URL: https://github.com/apache/camel-karavan/issues/749#issuecomment-1527082532

   > understood, but in practice, not all projects follow best practices.. some projects have legacy code whose artifacts are not in maven and libraries are stored in source controls. These libraries are added as file dependencies.
   > 
   > Also, sometimes the dependent library is not fully developed to be published in public or private maven, there should still be an option for users to try and test the logic in such a library. giving only the repository option, user is forced to finish their library work first and publish to Maven. Then only he can consume. This creates serialization of work and teams don't like serializing work. What if user just has a stub API in the library initially from another team. They will publish the library later once it's tested.
   
   Yeah that was also one of the reasons for the local JAR feature in jbang. IMHO allowing users to just drop what they need in the same folder, and then let jbang figure out how to run this, and export nicely into working maven/gradle based projects that can be used to continue, and also for jenkins/ci-cd pipelines to build and deploy from there.
   
   All in total making Karavan and Camel more approachable to users that want a quick and easy way to build small integrations and for users that need to prototype "stuff".
   
   I would like to consider reopening this and be able to offer this feature.


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