You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by GitBox <gi...@apache.org> on 2019/08/07 09:06:17 UTC

[GitHub] [camel-quarkus] ppalaga commented on issue #112: Add a parent pom for end user applications

ppalaga commented on issue #112: Add a parent pom for end user applications
URL: https://github.com/apache/camel-quarkus/issues/112#issuecomment-519011164
 
 
   > can’t we just fix the camel quarkus bom ?
   
   Yeah, it could work (although encouraging users to inherit from a BOM may sound strange; anyway, I do not think that's a big issue). I'd do it in such a way the users will be able to choose whether they want to (a) import the BOM or (b) use it as a parent. (b) would just bring some plugin config on top of (a).
   
   The main concern is to maintain the setup for end users separately from ours (for building camel extensions) so that we accidentally do not break their projects. 
   
   > about examples we could create a quickstart repo or put example so in quarkus one, git is simpler imho
   
   Having a separate git repo for quickstarts is perhaps easier for creating them but not for testing them and keeping them in sync with camel-quarkus. Exporting the itests automatically to a separate git repo(s) could solve the sync problem though. 

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