[GitHub] lburgazzoli commented on issue #500: feature(knative): support configmap and secrets

lburgazzoli commented on issue #500: feature(knative): support configmap and secrets URL: https://github.com/apache/camel-k/pull/500#issuecomment-468727814 should be better now This is an automated message from the Apache Git

[GitHub] lburgazzoli commented on a change in pull request #500: feature(knative): support configmap and secrets

lburgazzoli commented on a change in pull request #500: feature(knative): support configmap and secrets URL: https://github.com/apache/camel-k/pull/500#discussion_r261673530 ## File path: pkg/util/util.go ## @@ -18,12 +18,15 @@ limitations under the License. package util

[GitHub] nicolaferraro opened a new issue #516: Refactor roles to simplify them

nicolaferraro opened a new issue #516: Refactor roles to simplify them URL: https://github.com/apache/camel-k/issues/516 We currently have many roles as yaml files. The base one is installed in any platform, but it contains things that we don't manage. E.g. why requiring permissions for

Re: [VOTE] Release Apache Camel-K Runtime 0.3.0 (take 2)

+1 (binding) On Fri, Mar 1, 2019 at 10:02 AM Claus Ibsen wrote: > +1 (binding) > > On Wed, Feb 27, 2019 at 9:31 AM Andrea Cosentino > wrote: > > > > Hello all: > > > > This is a vote to release Apache Camel-K runtime 0.3.0 > > > > Staging repository: > > https://repository.apache.org/content/re

[GitHub] christophd opened a new issue #515: Allow file names as "kamel delete" argument

christophd opened a new issue #515: Allow file names as "kamel delete" argument URL: https://github.com/apache/camel-k/issues/515 I had a file called `telegramToKafka.groovy` and the integration was then named `telegram-to-kafka` which is fine but when I use `kamel delete` operation I can

[GitHub] lburgazzoli merged pull request #24: chore(netty): improve health service

lburgazzoli merged pull request #24: chore(netty): improve health service URL: https://github.com/apache/camel-k-runtime/pull/24 This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [camel-3] - core OSGi / XML

It sounds good to me. Regards JB Le 1 mars 2019 à 11:42, à 11:42, Francois Papon a écrit: >Ok, > >Can I push a PR for this? > >Regards, > >François Papon >fpa...@apache.org > >Le 01/03/2019 à 14:38, Claus Ibsen a écrit : >> Hi >> >> Yeah now that we have a core sub-folder, we can likely move th

Re: [camel-3] - core OSGi / XML

Ok, I created the Jira: https://issues.apache.org/jira/browse/CAMEL-13275 I will push the PR for review. Regards, François Papon fpa...@apache.org Le 01/03/2019 à 14:50, Claus Ibsen a écrit : > Hi > > Yeah but mind that moving them is not as easy, as the build assumes > they are in the compon

Re: [camel-3] - core OSGi / XML

Hi Yeah but mind that moving them is not as easy, as the build assumes they are in the components folder. So you need to adjust camel-blueprint and camel-spring too, and also in the camel-package-maven-plugin some some code for dealing with these 2 module names. I suggest to log a JIRA and then w

Re: [camel-3] - core OSGi / XML

Ok, Can I push a PR for this? Regards, François Papon fpa...@apache.org Le 01/03/2019 à 14:38, Claus Ibsen a écrit : > Hi > > Yeah now that we have a core sub-folder, we can likely move them in there. > > > On Fri, Mar 1, 2019 at 11:25 AM Francois Papon > wrote: >> Hi, >> >> I see on master th

[GitHub] kameshsampath closed issue #508: Update minikube docs

kameshsampath closed issue #508: Update minikube docs URL: https://github.com/apache/camel-k/issues/508 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the UR

[GitHub] kameshsampath commented on issue #508: Update minikube docs

kameshsampath commented on issue #508: Update minikube docs URL: https://github.com/apache/camel-k/issues/508#issuecomment-468622565 Yes Nicola has merged it I guess. Thank you This is an automated message from the Apache Gi

Re: [camel-3] - core OSGi / XML

Hi Yeah now that we have a core sub-folder, we can likely move them in there. On Fri, Mar 1, 2019 at 11:25 AM Francois Papon wrote: > > Hi, > > I see on master that this modules are under the "components" module: > > - camel-core-osgi > > - camel-core-xml > > Is there a reason to not put them u

[GitHub] lburgazzoli commented on issue #508: Update minikube docs

lburgazzoli commented on issue #508: Update minikube docs URL: https://github.com/apache/camel-k/issues/508#issuecomment-468618498 @kameshsampath I think this can be closed right ? This is an automated message from the Apache

[camel-3] - core OSGi / XML

Hi, I see on master that this modules are under the "components" module: - camel-core-osgi - camel-core-xml Is there a reason to not put them under the "core" module? Regards, -- François Papon fpa...@apache.org

[GitHub] lburgazzoli merged pull request #23: chore(camel-3): fix camel 3 compatibility layer

lburgazzoli merged pull request #23: chore(camel-3): fix camel 3 compatibility layer URL: https://github.com/apache/camel-k-runtime/pull/23 This is an automated message from the Apache Git Service. To respond to the message,

Re: [VOTE] Release Apache Camel-K Runtime 0.3.0 (take 2)

+1 (binding) On Wed, Feb 27, 2019 at 9:31 AM Andrea Cosentino wrote: > > Hello all: > > This is a vote to release Apache Camel-K runtime 0.3.0 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1122 > > Tag: > https://gitbox.apache.org/repos/asf?p=camel-k

Re: [VOTE] Release Apache Camel-K Runtime 0.3.0 (take 2)

+1 binding. I checked Signed key of the source artifacts. Build the source from without any error. LICENSE and NOTICE files look good. The staging repo artifacts look good Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Feb 27, 2019 at 4:38 PM Willem Jiang wrote: > > The Source rele

Re: [jira] [Commented] (CAMEL-12854) Provide a GraphQL component

I posted an answer there.  -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, February 28, 2019, 5:06:09 PM GMT+1, Zoran Regvart wrote: