Hi, Thank you for the quick response and for the help!
I wonder if it would be possible for the tooling (Camel JBang?) to handle the cases where additional Maven repositories are needed? As a person who mainly uses Karavan to create the integrations and Camel JBang as the tool to run them, I was quite clueless of what was going on. Couple quick ideas come to mind: * Maybe a quick dirty mapping directly coded into the tooling: If Jira is needed, automatically add Atlassian repo etc. * Some new metadata in the Kamelets / Components could be used to give the tooling the required information of additional repositories. I wonder, given there are hundreds of components, is the Jira/Atlassian a special case or are there some other component & repositories that will have the similar issues? Thanks again and have a nice weekend. Best regards, Mikael la 28. tammik. 2023 klo 19.40 Claus Ibsen (claus.ib...@gmail.com) kirjoitti: > > atlassian does not release to maven central so you need to add their maven > repo to jbang or have it pre downloaded. > > lør. 28. jan. 2023 kl. 17.54 skrev Mikael Koskinen <mijap...@gmail.com>: > > > Hi, > > > > I'm trying to get the Jira component to work but without success. The > > error I'm getting is: > > > > Caused by: java.lang.IllegalArgumentException: Cannot find component > > with name: jira. Did you mean: gora, irc, jcr, jpa, mina > > > > And from the stacktrace I can see the following: > > > > Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: > > The following artifacts could not be resolved: > > com.atlassian.sal:sal-api:jar:4.4.2, com.atlassian.jira:j > > ira-rest-java-client-api:jar:5.2.4, > > com.atlassian.jira:jira-rest-java-client-core:jar:5.2.4: Could not > > find artifact com.atlassian.sal:sal-api:jar:4.4.2 in central > > (https://r > > epo1.maven.org/maven2) > > at > > org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:431) > > ~[maven-resolver-impl-1.8.2.jar:1.8.2] > > at > > org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:235) > > ~[maven-resolver-impl-1.8.2.jar:1.8.2] > > at > > org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:357) > > ~[maven-resolver-impl-1.8.2.jar:1.8.2] > > at > > org.apache.camel.main.download.MavenDependencyDownloader.resolveDependenciesViaAether(MavenDependencyDownloader.java:1190) > > ~[camel-kamelet-main-3.20.1.jar:3.20.1] > > at > > org.apache.camel.main.download.MavenDependencyDownloader.lambda$doDownloadDependency$0(MavenDependencyDownloader.java:365) > > ~[camel-kamelet-main-3.20.1.jar:3.20.1] > > > > > > Here's a simple YAML to reproduce the issue: > > > > apiVersion: camel.apache.org/v1 > > kind: Integration > > metadata: > > name: logger-test > > spec: > > flows: > > - route: > > from: > > uri: jira:WATCHUPDATES > > parameters: > > jiraUrl: https://company.atlassian.net/jira > > jql: project=CamelTest > > steps: > > - to: > > uri: >- > > > > http://https://webhook.site/73458678-284f-4c01-a8b8-d3c09a7dfaaaa > > > > And here's one way to run it: > > > > jbang run "-Dcamel.jbang.version=3.20.1" --fresh camel@apache/camel > > run example.yaml > > > > Best regards, > > Mikael > > > -- > Claus Ibsen > ----------------- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
