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/03/24 12:34:27 UTC
[GitHub] [camel-quarkus] lburgazzoli opened a new issue #2368: catalog: include information about the camel artifact from which an extension is created
lburgazzoli opened a new issue #2368:
URL: https://github.com/apache/camel-quarkus/issues/2368
This would be useful because as today in camel-k you can declare a dependency by using the artifact id, so as example, to include the direct component you can use
kamel run integration.yaml -d camel-direct
With quarkus, you need to use the quarkus one, like:
kamel run integration.yaml -d camel-quarkus-direct
But since the runtime is an implementation detail, it would be nice to let users declaring dependencies using the camel artifact id and to make it possible we need to have the information about the artifact the extension has been created from.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2368: catalog: include information about the camel artifact from which an extension is created
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2368:
URL: https://github.com/apache/camel-quarkus/issues/2368#issuecomment-827670839
Blocked by https://github.com/apache/camel/pull/5471
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2368: catalog: include information about the camel artifact from which an extension is created
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2368:
URL: https://github.com/apache/camel-quarkus/issues/2368#issuecomment-846956403
Looking at this in greater detail, the entries (components, languages and data formats) in camel quarkus catalog have zero or one camel artifact they come from. I am implementing something like this:
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2368: catalog: include information about the camel artifact from which an extension is created
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2368:
URL: https://github.com/apache/camel-quarkus/issues/2368#issuecomment-827636250
Created https://issues.apache.org/jira/browse/CAMEL-16557
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2368: Store the association between Camel Quarkus Catalog items and Camel Catalog items
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2368:
URL: https://github.com/apache/camel-quarkus/issues/2368#issuecomment-847733455
Fixed via a1260cb1ed0b19dbfe6010621532e9be326df489
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2368: catalog: include information about the camel artifact from which an extension is created
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2368:
URL: https://github.com/apache/camel-quarkus/issues/2368#issuecomment-805840556
A Camel Quarkus extension can depend on zero to *n* Camel artifacts. Do you have an idea where/how to store that info?
Not sure adding a field to `org.apache.camel.tooling.model.ArtifactModel` is the best way to go. It would have little to no meaning in the context of Camel Core. Maybe we should add a free form map for this kind of ad hoc attributes that are only meaningful for Camel subprojects?
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga closed issue #2368: Store the association between Camel Quarkus Catalog items and Camel Catalog items
Posted by GitBox <gi...@apache.org>.
ppalaga closed issue #2368:
URL: https://github.com/apache/camel-quarkus/issues/2368
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] lburgazzoli commented on issue #2368: catalog: include information about the camel artifact from which an extension is created
Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on issue #2368:
URL: https://github.com/apache/camel-quarkus/issues/2368#issuecomment-805874860
I don't have any opinion about where to store such info, so generic attributes would work for me
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org