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 2020/10/09 16:49:44 UTC
[GitHub] [camel-quarkus] ppalaga opened a new issue #1898: Figure out how to maintain Camel components that bring too many non-convergent dependencies
ppalaga opened a new issue #1898:
URL: https://github.com/apache/camel-quarkus/issues/1898
Here is the list of components where the issue occurs: https://github.com/apache/camel-quarkus/issues?q=is%3Aissue+%5Bdependency+hell%5D
I see two options:
A. Keep enforcing dependencyConvergence, but manage in the extension instead of our global BoM
B. Stop enforcing dependencyConvergence for the given extensions
Both options have some potential to worsen the ability of the given extensions to combine flawlessly with the rest of the ecosystem. I think that's fine as long as it is documented.
Other ideas?
----------------------------------------------------------------
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 #1898: Figure out how to maintain Camel components that bring too many non-convergent dependencies
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1898:
URL: https://github.com/apache/camel-quarkus/issues/1898#issuecomment-716410141
With Spark, we went with A. there is an extension's own BOM that needs to get imported before any other Quarkus and Camel Quarkus BOMs in user apps.
----------------------------------------------------------------
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 #1898: Figure out how to maintain Camel components that bring too old or too many non-convergent dependencies
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1898:
URL: https://github.com/apache/camel-quarkus/issues/1898#issuecomment-719475261
I spoke with @aloubyansky and here is how we are going to proceed:
* We will implement a one-off platform for camel-quarkus-spark following this example: https://github.com/quarkusio/quarkus/tree/master/devtools/bom-descriptor-json
* The new platform can be registered at https://github.com/quarkusio/quarkus-extension-catalog/blob/master/platforms.json
* From there the new platform should be visible for Quarkus tooling. Some tools do not support this fully yet, e.g. code.quarkus.io - this may change in the future.
----------------------------------------------------------------
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 #1898: Figure out how to maintain Camel components that bring too old or too many non-convergent dependencies
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1898:
URL: https://github.com/apache/camel-quarkus/issues/1898#issuecomment-719477232
Note to myself: there is https://registry.quarkus.io/ able to list all available extensions and in the future possibly also platforms.
----------------------------------------------------------------
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 edited a comment on issue #1898: Figure out how to maintain Camel components that bring too many non-convergent dependencies
Posted by GitBox <gi...@apache.org>.
ppalaga edited a comment on issue #1898:
URL: https://github.com/apache/camel-quarkus/issues/1898#issuecomment-716410141
With Spark, we went with A. there is an extension's own BOM that needs to get imported before any other Quarkus and Camel Quarkus BOMs in user apps.
We discuss with the Quarkus team whether Quarkus project generator tooling could support extensions of this kind https://groups.google.com/forum/#!topic/quarkus-dev/1wRJONB0DjA
----------------------------------------------------------------
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 #1898: Figure out how to maintain Camel components that bring too old or too many non-convergent dependencies
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1898:
URL: https://github.com/apache/camel-quarkus/issues/1898#issuecomment-1036343963
We gave up on Spark https://github.com/apache/camel-quarkus/issues/3466
--
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
[GitHub] [camel-quarkus] ppalaga commented on issue #1898: Figure out how to maintain Camel components that bring too old or too many non-convergent dependencies
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1898:
URL: https://github.com/apache/camel-quarkus/issues/1898#issuecomment-723086673
Docs for creating platforms: https://github.com/quarkusio/quarkus/pull/13153
----------------------------------------------------------------
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