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/03/12 08:42:57 UTC

[GitHub] [camel-quarkus] oscerd commented on issue #878: Update to introduce the quarkus qute extension

oscerd commented on issue #878: Update to introduce the quarkus qute extension
URL: https://github.com/apache/camel-quarkus/pull/878#issuecomment-598070078
 
 
   > Is there a general agreement that the Qute component is rather unlikely to ever get moved to Camel? I mean there is a technical reason that will hardly change in the future: the Qute engine is hard to run outside Quarkus, right? I am asking because otherwise it would be cleaner to keep the component in a separate maven module.
   
   The reason is the following https://github.com/apache/camel/pull/3605#issuecomment-595416181
   It's more related to releasing.

----------------------------------------------------------------
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


With regards,
Apache Git Services