Done this morning.
The 2.x branch is now called camel-2.x, while master has been moved to what we
had in sandbox/camel-3.x
--Andrea Cosentino --Apache Camel PMC
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail:
ancosen1985@yahoo.comTwitter:
Done.
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Wednesday, December 19, 2018, 8:23:20 AM GMT+1, Andrea Cosentino
wrote:
I'm just
I'm just starting to doing these operations.
Please hold on on pushing until I finish.
I'll update the situation in this thread.
Thanks
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email:
crystaldust opened a new issue #306: The kaniko build pod failed to start
URL: https://github.com/apache/camel-k/issues/306
I installed camel-k with `kamel install` and all the language build env pods
seem to fail, complaining no Dockerfile is specified, the logs look like so:
```bash
Awesome job, Francois! That's really modern & cool web site!
On Tue, Dec 18, 2018 at 9:06 PM Francois Papon
wrote:
> Cool!
>
> I will push a PR for the responsive soon.
>
> Regards,
>
> François Papon
> fpa...@apache.org
>
> Le 18/12/2018 à 15:51, Zoran Regvart a écrit :
> > Thank you
Yes, I can cut a release this weekend.
Thanks,
Gregor
On Tue, Dec 18, 2018, 2:01 PM Andrea Cosentino
+1.
>
> Gregor are you available for this release?
>
> Thanks
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache
nicolaferraro opened a new issue #305: Allow to customize integration service
account
URL: https://github.com/apache/camel-k/issues/305
In some cases (e.g. Knative event sources allow that) it's handy to allow to
customize the service account used to run the integration.
e.g. a
lburgazzoli opened a new pull request #304: Display relevant custom columns
URL: https://github.com/apache/camel-k/pull/304
Fixes #274
This is an automated message from the Apache Git Service.
To respond to the message,
lburgazzoli edited a comment on issue #300: add resources to an integration
URL: https://github.com/apache/camel-k/pull/300#issuecomment-448229240
yes we should.
The main problem here is that there are differences between knative and
other environments so the `platform` protocol has
lburgazzoli edited a comment on issue #300: add resources to an integration
URL: https://github.com/apache/camel-k/pull/300#issuecomment-448229240
yes we should.
The main problem here is that there are differences between knative and
other environments so the `platform` protocol has
lburgazzoli edited a comment on issue #300: add resources to an integration
URL: https://github.com/apache/camel-k/pull/300#issuecomment-448229240
yes we should.
The main problem here is that there are differences between knative and
other environments so the `platform` protocol has
lburgazzoli commented on issue #300: add resources to an integration
URL: https://github.com/apache/camel-k/pull/300#issuecomment-448229240
yes we should.
The main problem here is that there are differences between knative and
other environments so the `platform` protocol has to be
davsclaus commented on issue #300: add resources to an integration
URL: https://github.com/apache/camel-k/pull/300#issuecomment-448227884
I think we can also add support for `env:` to Apache Camel's
`ResourceHelper` and maybe also JVM system properties, then we got _all of them
covered_
lburgazzoli commented on issue #300: add resources to an integration
URL: https://github.com/apache/camel-k/pull/300#issuecomment-448221098
@nicolaferraro
ok, so I've added support for looking up resources using env vars. using
camel dsl it should look like:
```java
davsclaus commented on issue #249: Add support for template endpoint
URL: https://github.com/apache/camel-k/issues/249#issuecomment-448220699
Yeah its not so often in use, it was actually created when James and I was
tired of getting a bunch of sample XML routes / Java Routes from end
lburgazzoli commented on issue #303: catalog : include camel-k components
URL: https://github.com/apache/camel-k/pull/303#issuecomment-448220591
yes, I've hard coded them inside the catalog so no code change is required
in camel-k once they are moved in standard catalog
nicolaferraro commented on issue #249: Add support for template endpoint
URL: https://github.com/apache/camel-k/issues/249#issuecomment-448215395
Yeah, I've never used it, but I see it has a different behavior than the one
we require here.
davsclaus commented on issue #249: Add support for template endpoint
URL: https://github.com/apache/camel-k/issues/249#issuecomment-448214477
Oh the stub component will not create an actual endpoint of what endpoint
uri is defined. So in your example with knative then stub will not create
+1.
Gregor are you available for this release?
Thanks
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Tuesday, December 18, 2018, 1:59:45 PM
nicolaferraro commented on issue #249: Add support for template endpoint
URL: https://github.com/apache/camel-k/issues/249#issuecomment-448212864
I was looking in the Camel catalog and I've found a similar component that
we may be able to reuse:
Hi
We have 15 JIRAs resolved for Camel 2.21.4. And we have just recently
released 2.23.0, which means that we should EOL the 2.21.x branch
soonish.
So maybe we should try to get 2.21.4 released soon.
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2:
davsclaus commented on issue #302: catalog should be available as cutom resource
URL: https://github.com/apache/camel-k/issues/302#issuecomment-448211258
Ah is this a step in the direction to support mixing different Camel
versions in the same namespace.
davsclaus commented on issue #303: catalog : include camel-k components
URL: https://github.com/apache/camel-k/pull/303#issuecomment-448210699
I guess this is fine to hardcode the extra components - one day they may be
moved to the parent Apache Camel project and included there OOTB and
davsclaus commented on issue #249: Add support for template endpoint
URL: https://github.com/apache/camel-k/issues/249#issuecomment-448209161
@nicolaferraro I think this is a good idea, and since the `template`
component is a component then its not a drastic change in camel-core etc, and
davsclaus commented on issue #249: Add support for template endpoint
URL: https://github.com/apache/camel-k/issues/249#issuecomment-448208566
Okay so template from Camel point of view is just like any other Camel
component. The template component is then capable of referring to an actual
Cool!
I will push a PR for the responsive soon.
Regards,
François Papon
fpa...@apache.org
Le 18/12/2018 à 15:51, Zoran Regvart a écrit :
> Thank you François, I merged your PR to camel-website master and it's
> now on staging:
>
> https://camel.apache.org/staging/
>
> looks pretty good :)
>
>
Thank you François, I merged your PR to camel-website master and it's
now on staging:
https://camel.apache.org/staging/
looks pretty good :)
zoran
On Mon, Dec 17, 2018 at 11:19 AM Francois Papon
wrote:
>
> Hi,
>
> Thanks for your feeback!
>
> For the mobile responsive, I didn't work on it yet
zregvart closed pull request #3: [CAMEL-12998] Website design proposal
URL: https://github.com/apache/camel-website/pull/3
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull
fpapon opened a new pull request #3: [CAMEL-12998] Website design proposal
URL: https://github.com/apache/camel-website/pull/3
This is a first round about website design proposal.
This is an automated message from the Apache
lburgazzoli commented on issue #300: add resources to an integration
URL: https://github.com/apache/camel-k/pull/300#issuecomment-448163949
I've fixed the typo but for knative we have an issue as we can expose
resources as env var but then we can't use standard java resource loading
lburgazzoli opened a new pull request #303: catalog : include camel-k components
URL: https://github.com/apache/camel-k/pull/303
Fixes #301
This is an automated message from the Apache Git Service.
To respond to the message,
nicolaferraro commented on a change in pull request #300: add resources to an
integration
URL: https://github.com/apache/camel-k/pull/300#discussion_r242436216
##
File path: pkg/builder/builder_types.go
##
@@ -147,8 +147,7 @@ type Context struct {
Artifacts
On Mon, Dec 17, 2018 at 3:32 PM Andrea Cosentino
wrote:
>
> If it works for everyone the next steps should be:
>
> - On Wednesday morning I'll send an email with an alert about the creation of
> 2.x branch from master
> - I'll move sanbox/camel-3.x to master shortly after pushing 2.x
>
> Does
33 matches
Mail list logo
