Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let dependencies be defined using file URLs #1227

Closed
lburgazzoli opened this issue Jan 24, 2020 · 2 comments · Fixed by #2835
Closed

Let dependencies be defined using file URLs #1227

lburgazzoli opened this issue Jan 24, 2020 · 2 comments · Fixed by #2835
Labels
help wanted Extra attention is needed
Milestone

Comments

@lburgazzoli
Copy link
Contributor

As today we do allow to specify dependencies that are available through a maven repository but it should be possible to specify a local developer dependency, like:

kamel run integration.java --dependency file:/path/to/my-dep.jar

Under the hood the dependency should be:

  • uploaded to a s3 compatible object storage (i.e. https://min.io) following the maven repo layout
  • consumed by camel-k as any other dependency using an s3 wagon.
@johnpoth
Copy link
Member

I can take a look at this if it's ok

@nicolaferraro nicolaferraro modified the milestones: 1.3.0, 1.4.0 Dec 22, 2020
@johnpoth
Copy link
Member

johnpoth commented Feb 9, 2021

To alleviate the constraint of a S3 compatible storage, I was thinking of storing the dependency in a configmap (or an image layer..), WDYT ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants