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 2019/10/25 19:39:27 UTC
[GitHub] [camel-quarkus] gnodet commented on issue #336: Make the maven
plugin depend on the camel package-maven-plugin
gnodet commented on issue #336: Make the maven plugin depend on the camel package-maven-plugin
URL: https://github.com/apache/camel-quarkus/issues/336#issuecomment-546486191
Sure, that can be investigated. I haven't really checked how the model is used, but I don't think Camel should be tied to any Camel Quarkus concept, else it will be hard to maintain.
However, reusable code should stay in Camel, I agree.
Basically, we should keep the 2 mojos because they are specific to camel-quarkus and reuse the helpers and model classes from the camel plugin. So we'd be left with `PrepareCatalogQuarkusMojo` and `UpdateDocExtensionsListMojo` classes. Not sure we can do better.
----------------------------------------------------------------
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