-
Notifications
You must be signed in to change notification settings - Fork 344
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
Support of 3rd party camel components, data formats and type converters #1285
Comments
This should work out of the box as under the hoods your code is executed by a standard camel application: did you experience any issue ? |
I think the reporter asked on Camel mailing list, and it was about camel k auto-discovering 3rd party components in the DSL and automatic could map it to maven coordinates. That wont work out of the box. And it would require for example to support installing custom catalog's or something with metadata that describe component scheme/name and its mvn coordinate etc. |
Hi Luca, currently I have the problem that if I pass my dependency with the -d option, an error occurs.
Normal Scheduled default-scheduler Successfully assigned default/camel-k-kit-bp750vabvegtmhqbb5dg-builder to minikube Do you have any idea what the problem could be? |
@cenitfish can you post the log of the builder pod ? there should be an error there |
@lburgazzoli |
@lburgazzoli |
Can you check that the repository is listed among those used by camel-k ? there is a config map named |
@lburgazzoli |
To list all the configmap in your namespace: |
@lburgazzoli |
can you post the content of the integration platform ? I think when you did · |
It's difficult to see the logs because now the maven build is done in an init container and kubectl only display it if you specify the name of the container explicitly.. it should be Another reason to switch to an embedded build model for I'd also try to fix the issue that cause the resources not to be replaced when already present in RC2. |
We may want to have |
Right, that's a side effect of using init containers.
Yes, that won't rely on init containers. |
@cenitfish did you get it working ? |
@igarashitm I updated the config map "camel-k-maven-settings" and my repository is now included. Unfortunately I still get the error: I have no idea what's wrong. |
After the Camel Reinstall (without updated config map) it now seems to work. I continue with my tests. I'll be in touch when I'm done. |
@cenitfish can we close this issue ? |
yes. thx! |
Hello everybody,
Camel K is a cool thing and I think the world was just waiting for it. I have been working with Camel for a long time and have written numerous components for my customers. My question is - are the 3rd party camel components, data formats, type converters also supported and if so how can I use it?
Register new Maven Repository:
kamel install --maven-repository http://myserver:8081/nexus/content/repositories/myrepo@id=myrepo
Example route:
from('mycomponent://foo').to('mock:result')
Run the example route with 3rd party camel components, camel dataformats, camel typeconverter:
kamel run -d mvn:mycompany:mycomponent:1.0 hello.groovy --dev
It would be great if that were possible.
Best wishes
Alex
The text was updated successfully, but these errors were encountered: