ppalaga commented on issue #112: Add a parent pom for end user applications
URL: https://github.com/apache/camel-quarkus/issues/112#issuecomment-519023900
 
 
   > > 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.
   > 
   > we do have the build parent for internal use, isn’t it ?
   
   Yes, that's a good starting point, but there is some plugin config and props 
defined in the top level `camel-quarkus-parent` that need a closer look whether 
they are relevant to end users and/or how much danger do we risk keeping it 
there and passing it to end users via the BOM.
   
   > I’m not sold with the idea that our itest ate also examples as we do use 
itest to unit test native image so I’m more for real examples
   
   Yes, we do use itests to unit test native image, but that's a good thing, 
even for examples, is it not? I believe examples should be tested to ensure 
they keep working.
   
   Why do you think our itests are not "real" examples?
   

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to