Re: [HEADS UP] Camel K is here!
YAY! -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Wednesday, October 17, 2018, 12:24:37 AM GMT+2, Nicola Ferraro wrote: Hi folks, after some months of brainstorming with the community and a bit more than one month of development, our Camel K project has reached a good level of stability and I've published the first blog post about it yesterday. For those of you who haven't heard of Camel K, it's now a subproject of Apache Camel (https://github.com/apache/camel-k) with the target of building a lightweight runtime for running integration code directly on cloud platforms like Kubernetes and Openshift. It was inspired by "serverless" principles and it will also target Knative shortly. With the exception of the runtime code, that remains the good old Camel Java framework with 200+ components and full of EIPs, most of the "operator" code in Camel K is written in Go. But the new language has not stopped many adventurer Camel developers that have actively contributed to the project during last month. We still have a long way in front of us, let's continue to make Camel great! So, please.. check the project out! Spread it to the world! And provide your feedback, so we can make it always better. We love any kind of contribution! Links follow.. Announcement: https://twitter.com/ni_ferraro/status/1051872786946363392 Article: https://www.nicolaferraro.me/2018/10/15/introducing-camel-k/ Home: https://github.com/apache/camel-k Nicola
Re: [HEADS UP] Camel K is here!
Congratulations! This is an amazing work! regards, François Papon fpa...@apache.org Le 17/10/2018 à 02:24, Nicola Ferraro a écrit : > Hi folks, > after some months of brainstorming with the community and a bit more than > one month of development, our Camel K project has reached a good level of > stability and I've published the first blog post about it yesterday. > > For those of you who haven't heard of Camel K, it's now a subproject of > Apache Camel (https://github.com/apache/camel-k) with the target of > building a lightweight runtime for running integration code directly on > cloud platforms like Kubernetes and Openshift. It was inspired by > "serverless" principles and it will also target Knative shortly. > > With the exception of the runtime code, that remains the good old Camel > Java framework with 200+ components and full of EIPs, most of the > "operator" code in Camel K is written in Go. But the new language has not > stopped many adventurer Camel developers that have actively contributed to > the project during last month. We still have a long way in front of us, > let's continue to make Camel great! > > So, please.. check the project out! Spread it to the world! > And provide your feedback, so we can make it always better. We love any > kind of contribution! > > Links follow.. > > Announcement: https://twitter.com/ni_ferraro/status/1051872786946363392 > Article: https://www.nicolaferraro.me/2018/10/15/introducing-camel-k/ > Home: https://github.com/apache/camel-k > > Nicola >
[HEADS UP] Camel K is here!
Hi folks, after some months of brainstorming with the community and a bit more than one month of development, our Camel K project has reached a good level of stability and I've published the first blog post about it yesterday. For those of you who haven't heard of Camel K, it's now a subproject of Apache Camel (https://github.com/apache/camel-k) with the target of building a lightweight runtime for running integration code directly on cloud platforms like Kubernetes and Openshift. It was inspired by "serverless" principles and it will also target Knative shortly. With the exception of the runtime code, that remains the good old Camel Java framework with 200+ components and full of EIPs, most of the "operator" code in Camel K is written in Go. But the new language has not stopped many adventurer Camel developers that have actively contributed to the project during last month. We still have a long way in front of us, let's continue to make Camel great! So, please.. check the project out! Spread it to the world! And provide your feedback, so we can make it always better. We love any kind of contribution! Links follow.. Announcement: https://twitter.com/ni_ferraro/status/1051872786946363392 Article: https://www.nicolaferraro.me/2018/10/15/introducing-camel-k/ Home: https://github.com/apache/camel-k Nicola
[GitHub] nicolaferraro closed pull request #181: chore(logging): move log colouring definition to runtime
nicolaferraro closed pull request #181: chore(logging): move log colouring
definition to runtime
URL: https://github.com/apache/camel-k/pull/181
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 request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/Gopkg.lock b/Gopkg.lock
index 26413b2..0c22817 100644
--- a/Gopkg.lock
+++ b/Gopkg.lock
@@ -25,18 +25,6 @@
pruneopts = "NUT"
revision = "de5bf2ad457846296e2031421a34e2568e304e35"
-[[projects]]
- digest = "1:69ebf3eaf09a9528d0fa78baecf58a816acd73b6b500eb714c54b9d8a01cff0c"
- name = "github.com/arsham/blush"
- packages = [
-"blush",
-"internal/reader",
-"internal/tools",
- ]
- pruneopts = "NUT"
- revision = "a87294e47998d46b608c76cecb35b712103ad45b"
- version = "v0.5.3"
-
[[projects]]
branch = "master"
digest = "1:707ebe952a8b3d00b343c01536c79c73771d100f63ec6babeaed5c79e2b8a8dd"
@@ -751,7 +739,6 @@
analyzer-name = "dep"
analyzer-version = 1
input-imports = [
-"github.com/arsham/blush/blush",
"github.com/fatih/structs",
"github.com/mitchellh/mapstructure",
"github.com/openshift/api/apps/v1",
diff --git a/pkg/util/log/util.go b/pkg/util/log/util.go
index 05a83db..c32ae15 100644
--- a/pkg/util/log/util.go
+++ b/pkg/util/log/util.go
@@ -25,7 +25,6 @@ import (
"os"
"github.com/apache/camel-k/pkg/apis/camel/v1alpha1"
- "github.com/arsham/blush/blush"
)
// Print prints integrations logs to the stdout
@@ -33,25 +32,7 @@ func Print(ctx context.Context, integration
*v1alpha1.Integration) error {
scraper := NewSelectorScraper(integration.Namespace,
"camel.apache.org/integration="+integration.Name)
reader := scraper.Start(ctx)
- b := {
- Finders: []blush.Finder{
- blush.NewExact("FATAL", blush.Red),
- blush.NewExact("ERROR", blush.Red),
- blush.NewExact("WARN", blush.Yellow),
- blush.NewExact("INFO", blush.Green),
- blush.NewExact("DEBUG", blush.Colour{
- Foreground: blush.RGB{R: 170, G: 170, B: 170},
- Background: blush.NoRGB,
- }),
- blush.NewExact("TRACE", blush.Colour{
- Foreground: blush.RGB{R: 170, G: 170, B: 170},
- Background: blush.NoRGB,
- }),
- },
- Reader: ioutil.NopCloser(reader),
- }
-
- if _, err := io.Copy(os.Stdout, b); err != nil {
+ if _, err := io.Copy(os.Stdout, ioutil.NopCloser(reader)); err != nil {
fmt.Println(err.Error())
}
diff --git a/runtime/jvm/src/main/resources/log4j2.properties
b/runtime/jvm/src/main/resources/log4j2.properties
index 9d5f10e..9f0f4b1 100644
--- a/runtime/jvm/src/main/resources/log4j2.properties
+++ b/runtime/jvm/src/main/resources/log4j2.properties
@@ -1,7 +1,7 @@
appender.console.type = Console
appender.console.name = console
appender.console.layout.type = PatternLayout
-appender.console.layout.pattern = [%-5level] %d{-MM-dd HH:mm:ss.SSS} [%t]
%c{1} - %msg%n
+appender.console.layout.pattern = %d{-MM-dd HH:mm:ss.SSS}
%highlight{%-5level} [%t] %c{1} - %msg%n
rootLogger.level = INFO
rootLogger.appenderRef.stdout.ref = console
\ No newline at end of file
diff --git a/vendor/github.com/arsham/blush/LICENSE
b/vendor/github.com/arsham/blush/LICENSE
deleted file mode 100644
index 03bc557..000
--- a/vendor/github.com/arsham/blush/LICENSE
+++ /dev/null
@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2018 Arsham Shirvani
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
diff --git a/vendor/github.com/arsham/blush/blush/blush.go
[GitHub] camel pull request #2568: [CAMEL-12605] Updated signature algorithms support...
GitHub user punkhorn opened a pull request: https://github.com/apache/camel/pull/2568 [CAMEL-12605] Updated signature algorithms supported and refactored API. You can merge this pull request into a Git repository by running: $ git pull https://github.com/punkhorn/camel-upstream master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2568.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2568 commit 35e3c22d33f18052c47a8023ac1e7c5b9d56ee22 Author: William Collins Date: 2018-10-16T18:45:07Z [CAMEL-12605] Updated signature algorithms supported and refactored API. ---
[GitHub] camel pull request #2567: CAMEL-12888: Fixed the short java type generation ...
GitHub user aldettinger opened a pull request: https://github.com/apache/camel/pull/2567 CAMEL-12888: Fixed the short java type generation in camel-package-ma⦠â¦ven-plugin More details in [CAMEL-12888](https://issues.apache.org/jira/browse/CAMEL-12888). You can merge this pull request into a Git repository by running: $ git pull https://github.com/aldettinger/camel master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2567.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2567 commit fc76cae5634ae7961644f92cfad0e475680a Author: aldettinger Date: 2018-10-16T18:03:56Z CAMEL-12888: Fixed the short java type generation in camel-package-maven-plugin ---
Re: Release Camel 2.23.0
+1 On Tue, Oct 16, 2018 at 11:31 AM Zoran Regvart wrote: > Hi Cameleers, > yeah I did some preliminary work, I need to finish that and cherry > pick it to `master` from `java-10` branch, > > zoran > > On Tue, Oct 16, 2018 at 9:57 AM, David Karlsen > wrote: > > Would it be worthwhile testing against 2.1.0.M4 in the mean time > > https://github.com/spring-projects/spring-boot/releases. > > This also brings Spring 5.1 - in order to do any preliminary testing? > > > > Den tir. 16. okt. 2018 kl. 09:52 skrev Andrea Cosentino > > : > > > >> Yeah, 2.1.0 ETA is 29 October > >> > >> https://github.com/spring-projects/spring-boot/milestones > >> > >> -- > >> Andrea Cosentino > >> -- > >> Apache Camel PMC Chair > >> Apache Karaf Committer > >> Apache Servicemix PMC Member > >> Email: ancosen1...@yahoo.com > >> Twitter: @oscerd2 > >> Github: oscerd > >> > >> > >> > >> > >> > >> > >> On Tuesday, October 16, 2018, 9:49:56 AM GMT+2, Claus Ibsen < > >> claus.ib...@gmail.com> wrote: > >> > >> > >> > >> > >> > >> On Mon, Oct 15, 2018 at 7:55 AM Andrea Cosentino > >> wrote: > >> > > >> > Hello all, > >> > I think it's time to release 2.23.0 since we introduced some new stuff > >> and fixed some bugs. > >> > What do you think? > >> > Gregor, are you able to work on releasing Camel 2.23.0 by the end of > >> October/beginning of November? > >> > Thanks. > >> > >> Yeah if we can time this after Spring Boot 2.1 release, so Camel 2.23 > >> is up to date with that release, then that would be great. > >> > >> > >> > >> > --Andrea Cosentino --Apache Camel PMC > >> ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: > >> ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd > >> > >> > >> > >> > >> -- > >> Claus Ibsen > >> - > >> http://davsclaus.com @davsclaus > >> Camel in Action 2: https://www.manning.com/ibsen2 > >> > > > > > > -- > > -- > > David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen > > > > -- > Zoran Regvart >
Re: Release Camel 2.23.0
Hi Cameleers, yeah I did some preliminary work, I need to finish that and cherry pick it to `master` from `java-10` branch, zoran On Tue, Oct 16, 2018 at 9:57 AM, David Karlsen wrote: > Would it be worthwhile testing against 2.1.0.M4 in the mean time > https://github.com/spring-projects/spring-boot/releases. > This also brings Spring 5.1 - in order to do any preliminary testing? > > Den tir. 16. okt. 2018 kl. 09:52 skrev Andrea Cosentino > : > >> Yeah, 2.1.0 ETA is 29 October >> >> https://github.com/spring-projects/spring-boot/milestones >> >> -- >> Andrea Cosentino >> -- >> Apache Camel PMC Chair >> Apache Karaf Committer >> Apache Servicemix PMC Member >> Email: ancosen1...@yahoo.com >> Twitter: @oscerd2 >> Github: oscerd >> >> >> >> >> >> >> On Tuesday, October 16, 2018, 9:49:56 AM GMT+2, Claus Ibsen < >> claus.ib...@gmail.com> wrote: >> >> >> >> >> >> On Mon, Oct 15, 2018 at 7:55 AM Andrea Cosentino >> wrote: >> > >> > Hello all, >> > I think it's time to release 2.23.0 since we introduced some new stuff >> and fixed some bugs. >> > What do you think? >> > Gregor, are you able to work on releasing Camel 2.23.0 by the end of >> October/beginning of November? >> > Thanks. >> >> Yeah if we can time this after Spring Boot 2.1 release, so Camel 2.23 >> is up to date with that release, then that would be great. >> >> >> >> > --Andrea Cosentino --Apache Camel PMC >> ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: >> ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd >> >> >> >> >> -- >> Claus Ibsen >> - >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > > > -- > -- > David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen -- Zoran Regvart
Re: Release Camel 2.23.0
Would it be worthwhile testing against 2.1.0.M4 in the mean time https://github.com/spring-projects/spring-boot/releases. This also brings Spring 5.1 - in order to do any preliminary testing? Den tir. 16. okt. 2018 kl. 09:52 skrev Andrea Cosentino : > Yeah, 2.1.0 ETA is 29 October > > https://github.com/spring-projects/spring-boot/milestones > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Tuesday, October 16, 2018, 9:49:56 AM GMT+2, Claus Ibsen < > claus.ib...@gmail.com> wrote: > > > > > > On Mon, Oct 15, 2018 at 7:55 AM Andrea Cosentino > wrote: > > > > Hello all, > > I think it's time to release 2.23.0 since we introduced some new stuff > and fixed some bugs. > > What do you think? > > Gregor, are you able to work on releasing Camel 2.23.0 by the end of > October/beginning of November? > > Thanks. > > Yeah if we can time this after Spring Boot 2.1 release, so Camel 2.23 > is up to date with that release, then that would be great. > > > > > --Andrea Cosentino --Apache Camel PMC > ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: > ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd > > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
Re: Release Camel 2.23.0
Yeah, 2.1.0 ETA is 29 October https://github.com/spring-projects/spring-boot/milestones -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Tuesday, October 16, 2018, 9:49:56 AM GMT+2, Claus Ibsen wrote: On Mon, Oct 15, 2018 at 7:55 AM Andrea Cosentino wrote: > > Hello all, > I think it's time to release 2.23.0 since we introduced some new stuff and > fixed some bugs. > What do you think? > Gregor, are you able to work on releasing Camel 2.23.0 by the end of > October/beginning of November? > Thanks. Yeah if we can time this after Spring Boot 2.1 release, so Camel 2.23 is up to date with that release, then that would be great. > --Andrea Cosentino --Apache Camel PMC > ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: > ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Release Camel 2.23.0
On Mon, Oct 15, 2018 at 7:55 AM Andrea Cosentino wrote: > > Hello all, > I think it's time to release 2.23.0 since we introduced some new stuff and > fixed some bugs. > What do you think? > Gregor, are you able to work on releasing Camel 2.23.0 by the end of > October/beginning of November? > Thanks. Yeah if we can time this after Spring Boot 2.1 release, so Camel 2.23 is up to date with that release, then that would be great. > --Andrea Cosentino --Apache Camel PMC > ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: > ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
