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/08 17:13:02 UTC
[GitHub] [camel-quarkus] ppalaga opened a new issue #118: Decide how to
maintain examples
ppalaga opened a new issue #118: Decide how to maintain examples
URL: https://github.com/apache/camel-quarkus/issues/118
Followup of the discussion in https://github.com/apache/camel-quarkus/issues/112 and https://github.com/apache/camel-quarkus/pull/115
What we agreed upon with @lburgazzoli :
* We need examples
* Integration tests may test aspects that have no didactic value for the app developers so keeping the distinction between itests and examples makes sense
* Examples should have tests
Open questions:
1. Where should the examples be hosted? `camel-quarkus` (preferred by @ppalaga ) or elsewhere?
2. Should the tests in example projects be run for every PR in `camel-quarkus`?
* @ppalaga: yes definitely, to have a tight feedback and responsibility loop
* @lburgazzoli: no daily is enough, otherwise the CI would take long
----------------------------------------------------------------
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