[GitHub] [camel-k-runtime] lburgazzoli opened a new pull request #123: Allow endpoint DSL in Camel k
lburgazzoli opened a new pull request #123: Allow endpoint DSL in Camel k URL: https://github.com/apache/camel-k-runtime/pull/123 Fixes #122 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
[GitHub] [camel-quarkus] oscerd merged pull request #103: Rename the rest of java packages in itests
oscerd merged pull request #103: Rename the rest of java packages in itests URL: https://github.com/apache/camel-quarkus/pull/103 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
[GitHub] [camel-quarkus] oscerd commented on issue #103: Rename the rest of java packages in itests
oscerd commented on issue #103: Rename the rest of java packages in itests URL: https://github.com/apache/camel-quarkus/pull/103#issuecomment-517327791 Thanks 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
[GitHub] [camel-k-runtime] nicolaferraro opened a new issue #122: Allow endpoint DSL in Camel k
nicolaferraro opened a new issue #122: Allow endpoint DSL in Camel k URL: https://github.com/apache/camel-k-runtime/issues/122 It would be a nice to experiment it. Especially if IDE auto-completion can work with it. 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
Re: [DISCUSS] New Camel website, rump up to go live
Hi Yeah its great to see the new website is shaping up. I think we should work on the front page, and update the content and how we present to the world what Apache Camel is. There are some outdated content there, and its also a bit unclear what Apache Camel is ;) And we should work on a new getting started guide. Its very old and talks about downloading Camel. I think 99% would be using maven / gradle / or something like start spring boot etc. Also I noticed in the components page where the table shows the options, then the option name are very narrow and they get word wrapped. I think that column should be wider. On Thu, Aug 1, 2019 at 11:19 AM Zoran Regvart wrote: > > Hi Cameleers, > so it's been a while since we discussed the state of the new website, > so let me start by enumerating what we have done so far and then what > I think needs to be done for the website to go live. > > So what has been done: > > A lot. A lot of folk over almost two years helped with the website > effort and their help needs to be acknowledged. I'm sorry not to > mention everyone here as I would certainly forget someone. I do wish > to thank you all for your contributions. > > In points: > - content from the Confluence wiki has been (high 90% of it) cleaned > up and migrated to asciidoc format and is now maintained in the git > repository > - tools that maintain the documentation were developed (updating from > javadoc, moving/copying documents and maintaining indexes) > - initial website design was contributed and polished over time > - tools to build and develop the website were implemented and > integrated with the CI > - a lot of small paper-cut issues were resolved > > You can find the majority of these issues as subtasks of CAMEL-11492[1]. > > What I think needs to be done: > - gather more feedback on the staging website > (https://camel.apache.org/staging/) > - find/resolve any search engine issues (such as CAMEL-13800[2]) > > What I think would be good to do: > - more search engine optimization (like the microdata effort CAMEL-11494[3]) > - I'd like to polish the documentation a bit CAMEL-13780[3], if it > turns out not too much work split up the documentation into even > further modules (CAMEL-13812[4]) > - add search (CAMEL-11503) > - iron out any design/responsive layout issues > > I think we can work on the 'needs to be done' bits in the following > week and rump up the effort to replace the old website with the new > one currently present only on the staging. > > And depending on the feedback, that is if there are no large blocking > issues found, I think we can go live with the new website somewhere in > the middle of August. > > So, with that I would like to call to action, I'd like to have a list > of actionable issues we need to resolve for the go live of the new > website. > > If you can take a moment and have a look at the staging site > (https://camel.apache.org/staging/) and either by replying on the > thread or by creating a subtask on CAMEL-11492[1] with any issues that > you think need to be addressed before we go live. > > And, if you can contribute to this effort, by modifying the design, > improving the build tools, correcting the documentation please feel > free to do so. > > zoran > > [1] https://issues.apache.org/jira/browse/CAMEL-11492 > [2] https://issues.apache.org/jira/browse/CAMEL-13800 > [3] https://issues.apache.org/jira/browse/CAMEL-11494 > [4] https://issues.apache.org/jira/browse/CAMEL-13780 > [5] https://issues.apache.org/jira/browse/CAMEL-13812 > [6] https://issues.apache.org/jira/browse/CAMEL-11503 > > -- > Zoran Regvart -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [DISCUSS] New Camel website, rump up to go live
Hi, Agree, it would be nice if we could publish the new website this month :) regards, François fpa...@apache.org Le 01/08/2019 à 11:18, Zoran Regvart a écrit : > Hi Cameleers, > so it's been a while since we discussed the state of the new website, > so let me start by enumerating what we have done so far and then what > I think needs to be done for the website to go live. > > So what has been done: > > A lot. A lot of folk over almost two years helped with the website > effort and their help needs to be acknowledged. I'm sorry not to > mention everyone here as I would certainly forget someone. I do wish > to thank you all for your contributions. > > In points: > - content from the Confluence wiki has been (high 90% of it) cleaned > up and migrated to asciidoc format and is now maintained in the git > repository > - tools that maintain the documentation were developed (updating from > javadoc, moving/copying documents and maintaining indexes) > - initial website design was contributed and polished over time > - tools to build and develop the website were implemented and > integrated with the CI > - a lot of small paper-cut issues were resolved > > You can find the majority of these issues as subtasks of CAMEL-11492[1]. > > What I think needs to be done: > - gather more feedback on the staging website > (https://camel.apache.org/staging/) > - find/resolve any search engine issues (such as CAMEL-13800[2]) > > What I think would be good to do: > - more search engine optimization (like the microdata effort CAMEL-11494[3]) > - I'd like to polish the documentation a bit CAMEL-13780[3], if it > turns out not too much work split up the documentation into even > further modules (CAMEL-13812[4]) > - add search (CAMEL-11503) > - iron out any design/responsive layout issues > > I think we can work on the 'needs to be done' bits in the following > week and rump up the effort to replace the old website with the new > one currently present only on the staging. > > And depending on the feedback, that is if there are no large blocking > issues found, I think we can go live with the new website somewhere in > the middle of August. > > So, with that I would like to call to action, I'd like to have a list > of actionable issues we need to resolve for the go live of the new > website. > > If you can take a moment and have a look at the staging site > (https://camel.apache.org/staging/) and either by replying on the > thread or by creating a subtask on CAMEL-11492[1] with any issues that > you think need to be addressed before we go live. > > And, if you can contribute to this effort, by modifying the design, > improving the build tools, correcting the documentation please feel > free to do so. > > zoran > > [1] https://issues.apache.org/jira/browse/CAMEL-11492 > [2] https://issues.apache.org/jira/browse/CAMEL-13800 > [3] https://issues.apache.org/jira/browse/CAMEL-11494 > [4] https://issues.apache.org/jira/browse/CAMEL-13780 > [5] https://issues.apache.org/jira/browse/CAMEL-13812 > [6] https://issues.apache.org/jira/browse/CAMEL-11503 >
[GitHub] [camel-quarkus] asf-ci commented on issue #103: Rename the rest of java packages in itests
asf-ci commented on issue #103: Rename the rest of java packages in itests URL: https://github.com/apache/camel-quarkus/pull/103#issuecomment-517226149 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/camel-quarkus-pr/61/ 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
Re: [DISCUSS] New Camel website, rump up to go live
+1 to go live as soon as possible. Thanks everyone involved. Il giorno gio 1 ago 2019 alle ore 11:19 Zoran Regvart ha scritto: > Hi Cameleers, > so it's been a while since we discussed the state of the new website, > so let me start by enumerating what we have done so far and then what > I think needs to be done for the website to go live. > > So what has been done: > > A lot. A lot of folk over almost two years helped with the website > effort and their help needs to be acknowledged. I'm sorry not to > mention everyone here as I would certainly forget someone. I do wish > to thank you all for your contributions. > > In points: > - content from the Confluence wiki has been (high 90% of it) cleaned > up and migrated to asciidoc format and is now maintained in the git > repository > - tools that maintain the documentation were developed (updating from > javadoc, moving/copying documents and maintaining indexes) > - initial website design was contributed and polished over time > - tools to build and develop the website were implemented and > integrated with the CI > - a lot of small paper-cut issues were resolved > > You can find the majority of these issues as subtasks of CAMEL-11492[1]. > > What I think needs to be done: > - gather more feedback on the staging website > (https://camel.apache.org/staging/) > - find/resolve any search engine issues (such as CAMEL-13800[2]) > > What I think would be good to do: > - more search engine optimization (like the microdata effort > CAMEL-11494[3]) > - I'd like to polish the documentation a bit CAMEL-13780[3], if it > turns out not too much work split up the documentation into even > further modules (CAMEL-13812[4]) > - add search (CAMEL-11503) > - iron out any design/responsive layout issues > > I think we can work on the 'needs to be done' bits in the following > week and rump up the effort to replace the old website with the new > one currently present only on the staging. > > And depending on the feedback, that is if there are no large blocking > issues found, I think we can go live with the new website somewhere in > the middle of August. > > So, with that I would like to call to action, I'd like to have a list > of actionable issues we need to resolve for the go live of the new > website. > > If you can take a moment and have a look at the staging site > (https://camel.apache.org/staging/) and either by replying on the > thread or by creating a subtask on CAMEL-11492[1] with any issues that > you think need to be addressed before we go live. > > And, if you can contribute to this effort, by modifying the design, > improving the build tools, correcting the documentation please feel > free to do so. > > zoran > > [1] https://issues.apache.org/jira/browse/CAMEL-11492 > [2] https://issues.apache.org/jira/browse/CAMEL-13800 > [3] https://issues.apache.org/jira/browse/CAMEL-11494 > [4] https://issues.apache.org/jira/browse/CAMEL-13780 > [5] https://issues.apache.org/jira/browse/CAMEL-13812 > [6] https://issues.apache.org/jira/browse/CAMEL-11503 > > -- > Zoran Regvart >
[GitHub] [camel-k] apupier opened a new pull request #896: Include modeline in examples #895
apupier opened a new pull request #896: Include modeline in examples #895 URL: https://github.com/apache/camel-k/pull/896 it allows to benefit from tooling based on Camel Language Server Signed-off-by: Aurélien Pupier 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
[GitHub] [camel-quarkus] oscerd commented on issue #102: Add configuration for quarkus:create-extension mojo
oscerd commented on issue #102: Add configuration for quarkus:create-extension mojo URL: https://github.com/apache/camel-quarkus/pull/102#issuecomment-517205832 Thanks 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
[GitHub] [camel-quarkus] oscerd merged pull request #102: Add configuration for quarkus:create-extension mojo
oscerd merged pull request #102: Add configuration for quarkus:create-extension mojo URL: https://github.com/apache/camel-quarkus/pull/102 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
[GitHub] [camel-k] apupier opened a new issue #895: Include modeline in examples
apupier opened a new issue #895: Include modeline in examples URL: https://github.com/apache/camel-k/issues/895 including `// camel-k : language=xxx ` as first line in examples will allow users to benefit from Camel Language Server based tooling 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
[GitHub] [camel-quarkus] ppalaga commented on issue #9: quarkus-camel - Use MainSupport as base for running Camel
ppalaga commented on issue #9: quarkus-camel - Use MainSupport as base for running Camel URL: https://github.com/apache/camel-quarkus/issues/9#issuecomment-517204501 This should be easier to do now that we are on Camel 3.0.0.M4. Any hints or examples @davsclaus how to do that? 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
[GitHub] [camel-website] zregvart closed pull request #21: chore: GitHub deployments
zregvart closed pull request #21: chore: GitHub deployments URL: https://github.com/apache/camel-website/pull/21 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
[GitHub] [camel-quarkus] ppalaga commented on issue #24: "Multiple consumers for the same endpoint" after renaming packages in extensions/servlet/deployment/src/test/java
ppalaga commented on issue #24: "Multiple consumers for the same endpoint" after renaming packages in extensions/servlet/deployment/src/test/java URL: https://github.com/apache/camel-quarkus/issues/24#issuecomment-517203547 The issue is solved after upgrading to Quarkus 0.20.0, all test packages will be renamed after https://github.com/apache/camel-quarkus/pull/103 is merged. I think we can close this one. 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
[GitHub] [camel-quarkus] ppalaga opened a new pull request #103: Rename the rest of java packages in itests
ppalaga opened a new pull request #103: Rename the rest of java packages in itests URL: https://github.com/apache/camel-quarkus/pull/103 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
[DISCUSS] New Camel website, rump up to go live
Hi Cameleers, so it's been a while since we discussed the state of the new website, so let me start by enumerating what we have done so far and then what I think needs to be done for the website to go live. So what has been done: A lot. A lot of folk over almost two years helped with the website effort and their help needs to be acknowledged. I'm sorry not to mention everyone here as I would certainly forget someone. I do wish to thank you all for your contributions. In points: - content from the Confluence wiki has been (high 90% of it) cleaned up and migrated to asciidoc format and is now maintained in the git repository - tools that maintain the documentation were developed (updating from javadoc, moving/copying documents and maintaining indexes) - initial website design was contributed and polished over time - tools to build and develop the website were implemented and integrated with the CI - a lot of small paper-cut issues were resolved You can find the majority of these issues as subtasks of CAMEL-11492[1]. What I think needs to be done: - gather more feedback on the staging website (https://camel.apache.org/staging/) - find/resolve any search engine issues (such as CAMEL-13800[2]) What I think would be good to do: - more search engine optimization (like the microdata effort CAMEL-11494[3]) - I'd like to polish the documentation a bit CAMEL-13780[3], if it turns out not too much work split up the documentation into even further modules (CAMEL-13812[4]) - add search (CAMEL-11503) - iron out any design/responsive layout issues I think we can work on the 'needs to be done' bits in the following week and rump up the effort to replace the old website with the new one currently present only on the staging. And depending on the feedback, that is if there are no large blocking issues found, I think we can go live with the new website somewhere in the middle of August. So, with that I would like to call to action, I'd like to have a list of actionable issues we need to resolve for the go live of the new website. If you can take a moment and have a look at the staging site (https://camel.apache.org/staging/) and either by replying on the thread or by creating a subtask on CAMEL-11492[1] with any issues that you think need to be addressed before we go live. And, if you can contribute to this effort, by modifying the design, improving the build tools, correcting the documentation please feel free to do so. zoran [1] https://issues.apache.org/jira/browse/CAMEL-11492 [2] https://issues.apache.org/jira/browse/CAMEL-13800 [3] https://issues.apache.org/jira/browse/CAMEL-11494 [4] https://issues.apache.org/jira/browse/CAMEL-13780 [5] https://issues.apache.org/jira/browse/CAMEL-13812 [6] https://issues.apache.org/jira/browse/CAMEL-11503 -- Zoran Regvart
[GitHub] [camel-quarkus] asf-ci commented on issue #102: Add configuration for quarkus:create-extension mojo
asf-ci commented on issue #102: Add configuration for quarkus:create-extension mojo URL: https://github.com/apache/camel-quarkus/pull/102#issuecomment-517201940 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/camel-quarkus-pr/60/ 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
[GitHub] [camel-quarkus] lburgazzoli commented on issue #75: Include quarkus info in camel-catalog
lburgazzoli commented on issue #75: Include quarkus info in camel-catalog URL: https://github.com/apache/camel-quarkus/issues/75#issuecomment-517201347 It is broader that that as the catalog contains information about endpoint, the properties that each endpoint supports, its schema and so on so for quarkus it can also include info about the properties each extension supports and so on. 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
[GitHub] [camel-quarkus] oscerd commented on issue #37: Documentation
oscerd commented on issue #37: Documentation URL: https://github.com/apache/camel-quarkus/issues/37#issuecomment-517199969 No, it's not ok, because the information must be in a suitable format to be published on the camel website. So we need to take as example camel-k or camel 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
[GitHub] [camel-quarkus] ppalaga commented on issue #37: Documentation
ppalaga commented on issue #37: Documentation URL: https://github.com/apache/camel-quarkus/issues/37#issuecomment-517199465 I assume using the same asciidoc setup like they have in Quarkus is OK? 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
[GitHub] [camel-quarkus] ppalaga commented on issue #75: Include quarkus info in camel-catalog
ppalaga commented on issue #75: Include quarkus info in camel-catalog URL: https://github.com/apache/camel-quarkus/issues/75#issuecomment-517198206 Actually, what purpose should the Catalog serve? If the main use case is to answer the question > For given component *c* and Camel version *x.y.z*, which platforms (SB, Quarkus, WidlFly, ...) are supported? then I think all the necessary info is already available on Maven Central. The answer can be obtained by a script that joins camel BOM with the compatible platform BOMs. So we perhaps do not need feed that information into a git repository? Well at least not manually. There could be a service or a regular job that would aggregate that info and make it available in some suitable format. WDYT? 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
[GitHub] [camel-quarkus] oscerd closed issue #81: AWS Extensions integration test are not built as native
oscerd closed issue #81: AWS Extensions integration test are not built as native URL: https://github.com/apache/camel-quarkus/issues/81 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
[GitHub] [camel-quarkus] ppalaga edited a comment on issue #81: AWS Extensions integration test are not built as native
ppalaga edited a comment on issue #81: AWS Extensions integration test are not built as native URL: https://github.com/apache/camel-quarkus/issues/81#issuecomment-517189126 This is solved in the current master. Could you please close, @oscerd ? 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
[GitHub] [camel-quarkus] ppalaga commented on issue #81: AWS Extensions integration test are not built as native
ppalaga commented on issue #81: AWS Extensions integration test are not built as native URL: https://github.com/apache/camel-quarkus/issues/81#issuecomment-517189126 This is closed in the current master. Could you please close, @oscerd ? 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
[GitHub] [camel-quarkus] oscerd commented on issue #82: Env variable substitution doesn't work
oscerd commented on issue #82: Env variable substitution doesn't work URL: https://github.com/apache/camel-quarkus/issues/82#issuecomment-517188959 I will 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
[GitHub] [camel-quarkus] ppalaga commented on issue #82: Env variable substitution doesn't work
ppalaga commented on issue #82: Env variable substitution doesn't work URL: https://github.com/apache/camel-quarkus/issues/82#issuecomment-517187933 After #72 was merged, using `quarkus.camel.defer-init-phase=true` in application.properties should solve the problem. Could you please try it, @oscerd and eventually close this issue? 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
[GitHub] [camel-quarkus] ppalaga opened a new pull request #102: Add configuration for quarkus:create-extension mojo
ppalaga opened a new pull request #102: Add configuration for quarkus:create-extension mojo URL: https://github.com/apache/camel-quarkus/pull/102 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
[GitHub] [camel-quarkus] oscerd merged pull request #100: Upgrade quarkus to v0.20.0 plsu some cleanup
oscerd merged pull request #100: Upgrade quarkus to v0.20.0 plsu some cleanup URL: https://github.com/apache/camel-quarkus/pull/100 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
[GitHub] [camel-quarkus] oscerd merged pull request #101: chore(cleanup): remove ide-config
oscerd merged pull request #101: chore(cleanup): remove ide-config URL: https://github.com/apache/camel-quarkus/pull/101 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
[GitHub] [camel-quarkus] asf-ci commented on issue #101: chore(cleanup): remove ide-config
asf-ci commented on issue #101: chore(cleanup): remove ide-config URL: https://github.com/apache/camel-quarkus/pull/101#issuecomment-517172139 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/camel-quarkus-pr/59/ 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
[GitHub] [camel-quarkus] asf-ci commented on issue #100: Upgrade quarkus to v0.20.0 plsu some cleanup
asf-ci commented on issue #100: Upgrade quarkus to v0.20.0 plsu some cleanup URL: https://github.com/apache/camel-quarkus/pull/100#issuecomment-517155988 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/camel-quarkus-pr/58/ 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
[GitHub] [camel-k] bouskaJ opened a new pull request #894: External kamel bin testing
bouskaJ opened a new pull request #894: External kamel bin testing URL: https://github.com/apache/camel-k/pull/894 Enable to use existing 'kamel' binary for e2e testing. This feature can be useful to test already built distribution. 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
