Re: build camel-core JDK 11
No related to camel-core, but this commit
https://github.com/apache/camel/commit/dda0e4c5890d8e12b5895b8736e3819d0b095d08
can be reverted/dropped because groovy 2.5.3 should work on Java 11.
Am 06.11.2018 um 03:36 schrieb Onder SEZGIN:
Thanks Zoran. I can see you rebased already i ll try to give whole build a
go in a sandbox.
On Fri, Nov 2, 2018 at 4:16 PM Claus Ibsen wrote:
On Fri, Nov 2, 2018 at 2:04 PM Zoran Regvart wrote:
Hi Önder and Cameers,
I've just rebased and pushed additional changes on the `java-10-test`
branch. With this it should be possible to run:
`./mvnw -Pfastinstall clean install`
on Java 11.
since this is a milestone on getting Camel running on Java 11 I guess
I'm going to celebrate this a bit with an adult beverage...
I think Mr Camel would like that too. So I stashed some beers in the
fridge to celebrate in a few hours ;)
zoran
On Fri, Nov 2, 2018 at 9:42 AM, Zoran Regvart wrote:
Hi Önder,
yeah I that would be it; I've not forgotten about this (read: still
rebasing), hopefully will get to the bottom of it today. I hit a snag
with Scala component, and it takes a long time for the build to run...
zoran
On Fri, Nov 2, 2018 at 8:22 AM, Onder SEZGIN
wrote:
Hi Zoran,
it is ok now. apparently as i was not doing full build, i should have
installed parent/pom.xml otherwise camel-parent artifact from snapshot
repository was retrieved where the maven property was missing.
thanks.
On Thu, Nov 1, 2018 at 2:38 PM Onder SEZGIN
wrote:
I think it should have been defined. it is in paren/pom.xml.
Not sure why it is not detected.
On Thu, Nov 1, 2018 at 12:08 PM Zoran Regvart
wrote:
Hi Önder,
looks like the `annotation-api-version` Maven property is not
defined.
Is this on the `java-10-test` branch? I must have missed it when
rebasing on `master`, let me rebase and test locally now,
zoran
On Thu, Nov 1, 2018 at 3:19 AM, Onder SEZGIN
wrote:
Hi,
Has anybody tried to build camel-core locally with JDK-11?
First i got this error;
[ERROR] Failed to execute goal
org.apache.camel:camel-package-maven-plugin:2.23.0-SNAPSHOT:prepare-spring-boot-auto-configuration
(validate) on project camel-core: Execution validate of goal
org.apache.camel:camel-package-maven-plugin:2.23.0-SNAPSHOT:prepare-spring-boot-auto-configuration
failed: A required class was missing while executing
org.apache.camel:camel-package-maven-plugin:2.23.0-SNAPSHOT:prepare-spring-boot-auto-configuration:
javax/xml/bind/annotation/XmlTransient
Then, i ran mvn clean install -Pfastinstall
inside tooling/maven/camel-package-maven-plugin.
Later while trying to build camel-core, i got another error.
[INFO] ---
camel-package-maven-plugin:2.23.0-SNAPSHOT:generate-components-list
(components) @ camel-core ---
[WARNING] The POM for
javax.annotation:javax.annotation-api:jar:${annotation-api-version} is
missing, no dependency information available
[DEBUG] Dependency collection stats:
{ConflictMarker.analyzeTime=155216,
ConflictMarker.markTime=138430, ConflictMarker.nodeCount=155,
ConflictIdSorter.graphTime=86832,
ConflictIdSorter.topsortTime=122681,
ConflictIdSorter.conflictIdCount=58,
ConflictIdSorter.conflictIdCycleCount=0,
ConflictResolver.totalTime=15833299,
ConflictResolver.conflictItemCount=107,
DefaultDependencyCollector.collectTime=343830160,
DefaultDependencyCollector.transformTime=16495156}
[DEBUG]
org.apache.camel:camel-package-maven-plugin:jar:2.23.0-SNAPSHOT:
[DEBUG]
org.apache.camel:json-simple-ordered:jar:2.23.0-SNAPSHOT:compile
[DEBUG]com.github.mvel:mvel:jar:97071e83fb:compile
[DEBUG]org.apache.maven:maven-core:jar:2.2.1:compile
[DEBUG] org.apache.maven:maven-settings:jar:2.2.1:compile
[DEBUG]
org.apache.maven:maven-plugin-parameter-documenter:jar:2.2.1:compile
[DEBUG]
org.apache.maven.reporting:maven-reporting-api:jar:2.2.1:compile
[DEBUG]
org.apache.maven.doxia:doxia-sink-api:jar:1.1:compile
[DEBUG]
org.apache.maven.doxia:doxia-logging-api:jar:1.1:compile
[DEBUG] org.apache.maven:maven-profile:jar:2.2.1:compile
[DEBUG] org.apache.maven:maven-model:jar:2.2.1:compile
[DEBUG]
org.apache.maven:maven-repository-metadata:jar:2.2.1:compile
[DEBUG]
org.apache.maven:maven-error-diagnostics:jar:2.2.1:compile
[DEBUG] commons-cli:commons-cli:jar:1.2:compile
[DEBUG]
org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4:compile
[DEBUG]
org.apache.maven:maven-artifact-manager:jar:2.2.1:compile
[DEBUG]
backport-util-concurrent:backport-util-concurrent:jar:3.1:compile
[DEBUG] org.apache.maven:maven-monitor:jar:2.2.1:compile
[DEBUG] classworlds:classworlds:jar:1.1:compile
[DEBUG]
org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile
[DEBUG] org.sonatype.plexus:plexus-cipher:jar:1.4:compile
[DEBUG]org.apache.maven:maven-artifact:jar:2.2.1:compile
[DEBUG]org.apache.maven:maven-plugin-api:jar:2.2.1:compile
[DEBUG]
org.apache.maven:maven-plugin-descriptor:jar:2.2.1:compile
[DEBUG]
AW: UNSUBSCRIBE ME
It is important to send the unsubscribe mail from the same account which is registered. If you can not (e.g. because address has changed), you could tweak the unsubscribe adress. See http://ant.apache.org/mail.html#How%20to%20unsubscribe%20your%20old%20email%20address Jan > -Ursprüngliche Nachricht- > Von: Andrea Cosentino [mailto:ancosen1...@yahoo.com.INVALID] > Gesendet: Montag, 5. November 2018 15:53 > An: users-unsubscr...@camel.apache.org; dev- > unsubscr...@camel.apache.org; commits-unsubscr...@camel.apache.org; > issues-unsubscr...@camel.apache.org; dev@camel.apache.org > Cc: us...@camel.apache.org; comm...@camel.apache.org; > iss...@camel.apache.org > Betreff: Re: UNSUBSCRIBE ME > > I ask to infra to remove yourself. > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Monday, November 5, 2018, 3:41:18 PM GMT+1, Marc-André Roussil > wrote: > > > > > > I try several times to unsubscribe from your email. > > Dont send me back this url http://camel.apache.org/mailing- > lists.htmlhttp://camel.apache.org/mailing-lists.html > > UNSUBSCRIBE ME > > Thanks
Re: UNSUBSCRIBE ME
Hello Zoran, Yes, exactly. INFRA told me the same thing. https://issues.apache.org/jira/browse/INFRA-17215 They are asking an email with full headers -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Tuesday, November 6, 2018, 12:36:16 AM GMT+1, Zoran Regvart wrote: Hi Andrea, Cameleers, I don't see Marc-André on the dev or on the users mailing list (checked via dev-l...@camel.apache.org and users-l...@camel.apache.org), I tried to unsubscribe him via the moderator commands[1]. I'm not sure if that did it or INFRA fixed it or Marc-André found a way to unsubscribe. I've found this tool[2] to help with forming the remote command e-mail addresses. zoran [1] https://www.apache.org/dev/committers#problem_posts [2] https://whimsy.apache.org/committers/moderationhelper.cgi On Mon, Nov 5, 2018 at 3:52 PM, Andrea Cosentino wrote: > I ask to infra to remove yourself. -- Zoran Regvart
Re: build camel-core JDK 11
Thanks Zoran. I can see you rebased already i ll try to give whole build a
go in a sandbox.
On Fri, Nov 2, 2018 at 4:16 PM Claus Ibsen wrote:
> On Fri, Nov 2, 2018 at 2:04 PM Zoran Regvart wrote:
> >
> > Hi Önder and Cameers,
> > I've just rebased and pushed additional changes on the `java-10-test`
> > branch. With this it should be possible to run:
> >
> > `./mvnw -Pfastinstall clean install`
> >
> > on Java 11.
> >
> > since this is a milestone on getting Camel running on Java 11 I guess
> > I'm going to celebrate this a bit with an adult beverage...
> >
>
> I think Mr Camel would like that too. So I stashed some beers in the
> fridge to celebrate in a few hours ;)
>
> > zoran
> >
> > On Fri, Nov 2, 2018 at 9:42 AM, Zoran Regvart wrote:
> > > Hi Önder,
> > > yeah I that would be it; I've not forgotten about this (read: still
> > > rebasing), hopefully will get to the bottom of it today. I hit a snag
> > > with Scala component, and it takes a long time for the build to run...
> > >
> > > zoran
> > >
> > > On Fri, Nov 2, 2018 at 8:22 AM, Onder SEZGIN
> wrote:
> > >> Hi Zoran,
> > >> it is ok now. apparently as i was not doing full build, i should have
> > >> installed parent/pom.xml otherwise camel-parent artifact from snapshot
> > >> repository was retrieved where the maven property was missing.
> > >> thanks.
> > >>
> > >> On Thu, Nov 1, 2018 at 2:38 PM Onder SEZGIN
> wrote:
> > >>
> > >>> I think it should have been defined. it is in paren/pom.xml.
> > >>> Not sure why it is not detected.
> > >>>
> > >>> On Thu, Nov 1, 2018 at 12:08 PM Zoran Regvart
> wrote:
> > >>>
> > Hi Önder,
> > looks like the `annotation-api-version` Maven property is not
> defined.
> > Is this on the `java-10-test` branch? I must have missed it when
> > rebasing on `master`, let me rebase and test locally now,
> >
> > zoran
> >
> > On Thu, Nov 1, 2018 at 3:19 AM, Onder SEZGIN
> wrote:
> > > Hi,
> > >
> > > Has anybody tried to build camel-core locally with JDK-11?
> > >
> > > First i got this error;
> > >
> > > [ERROR] Failed to execute goal
> > >
> >
> org.apache.camel:camel-package-maven-plugin:2.23.0-SNAPSHOT:prepare-spring-boot-auto-configuration
> > > (validate) on project camel-core: Execution validate of goal
> > >
> >
> org.apache.camel:camel-package-maven-plugin:2.23.0-SNAPSHOT:prepare-spring-boot-auto-configuration
> > > failed: A required class was missing while executing
> > >
> >
> org.apache.camel:camel-package-maven-plugin:2.23.0-SNAPSHOT:prepare-spring-boot-auto-configuration:
> > > javax/xml/bind/annotation/XmlTransient
> > >
> > > Then, i ran mvn clean install -Pfastinstall
> > > inside tooling/maven/camel-package-maven-plugin.
> > >
> > > Later while trying to build camel-core, i got another error.
> > >
> > > [INFO] ---
> > >
> camel-package-maven-plugin:2.23.0-SNAPSHOT:generate-components-list
> > > (components) @ camel-core ---
> > > [WARNING] The POM for
> > >
> javax.annotation:javax.annotation-api:jar:${annotation-api-version} is
> > > missing, no dependency information available
> > > [DEBUG] Dependency collection stats:
> {ConflictMarker.analyzeTime=155216,
> > > ConflictMarker.markTime=138430, ConflictMarker.nodeCount=155,
> > > ConflictIdSorter.graphTime=86832,
> ConflictIdSorter.topsortTime=122681,
> > > ConflictIdSorter.conflictIdCount=58,
> > > ConflictIdSorter.conflictIdCycleCount=0,
> > > ConflictResolver.totalTime=15833299,
> > > ConflictResolver.conflictItemCount=107,
> > > DefaultDependencyCollector.collectTime=343830160,
> > > DefaultDependencyCollector.transformTime=16495156}
> > > [DEBUG]
> org.apache.camel:camel-package-maven-plugin:jar:2.23.0-SNAPSHOT:
> > > [DEBUG]
> > org.apache.camel:json-simple-ordered:jar:2.23.0-SNAPSHOT:compile
> > > [DEBUG]com.github.mvel:mvel:jar:97071e83fb:compile
> > > [DEBUG]org.apache.maven:maven-core:jar:2.2.1:compile
> > > [DEBUG] org.apache.maven:maven-settings:jar:2.2.1:compile
> > > [DEBUG]
> > >
> org.apache.maven:maven-plugin-parameter-documenter:jar:2.2.1:compile
> > > [DEBUG]
> > > org.apache.maven.reporting:maven-reporting-api:jar:2.2.1:compile
> > > [DEBUG]
> org.apache.maven.doxia:doxia-sink-api:jar:1.1:compile
> > > [DEBUG]
> > org.apache.maven.doxia:doxia-logging-api:jar:1.1:compile
> > > [DEBUG] org.apache.maven:maven-profile:jar:2.2.1:compile
> > > [DEBUG] org.apache.maven:maven-model:jar:2.2.1:compile
> > > [DEBUG]
> > org.apache.maven:maven-repository-metadata:jar:2.2.1:compile
> > > [DEBUG]
> org.apache.maven:maven-error-diagnostics:jar:2.2.1:compile
> > > [DEBUG] commons-cli:commons-cli:jar:1.2:compile
> > > [DEBUG]
> > >
>
Re: [VOTE] Release Apache Camel 2.22.2
+1, tested with personal projects On Mon, Nov 5, 2018 at 3:23 PM Thomas Diesler wrote: > +1 from wildfly-camel > > cheers > — thomas > > > On Nov 2, 2018, at 8:27 PM, Alex Dettinger > wrote: > > > > +1 (non-binding) > > Nice cut Gregor. > > > > Alex > > > > On Fri, Nov 2, 2018 at 1:43 PM Luca Burgazzoli > > wrote: > > > >> +1 (binding) > >> > >> --- > >> Luca Burgazzoli > >> > >> On Fri, Nov 2, 2018 at 1:31 PM Nicola Ferraro > >> wrote: > >>> > >>> +1 (binding) > >>> > >>> Thanks! > >>> > >>> On Fri, Nov 2, 2018 at 10:38 AM Francois Papon < > >> francois.pa...@openobject.fr> > >>> wrote: > >>> > +1 (non-binding) > > Thanks for the release! > > regards, > > François Papon > fpa...@apache.org > > Le 02/11/2018 à 10:23, Gregor Zurowski a écrit : > > Hi Everyone: > > > > This is a vote to release Apache Camel 2.22.2, a patch release for > >> the > > camel-2.22.x branch with 37 improvements and bug fixes. > > > > Release notes: > > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344006=12311211 > > > > Staging repository: > > > >> https://repository.apache.org/content/repositories/orgapachecamel-1113/ > > > > Tarballs: > > >> > https://repository.apache.org/content/repositories/orgapachecamel-1113/org/apache/camel/apache-camel/2.22.2/ > > > > Tag: > > >> > https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.22.2 > > > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binary as Apache Camel 2.22.2 > > [ ] -1 Veto the release (provide specific comments) > > > > The vote is open for at least 72 hours. > > > > Thanks, > > Gregor > > > >> > >
Re: UNSUBSCRIBE ME
Hi Andrea, Cameleers, I don't see Marc-André on the dev or on the users mailing list (checked via dev-l...@camel.apache.org and users-l...@camel.apache.org), I tried to unsubscribe him via the moderator commands[1]. I'm not sure if that did it or INFRA fixed it or Marc-André found a way to unsubscribe. I've found this tool[2] to help with forming the remote command e-mail addresses. zoran [1] https://www.apache.org/dev/committers#problem_posts [2] https://whimsy.apache.org/committers/moderationhelper.cgi On Mon, Nov 5, 2018 at 3:52 PM, Andrea Cosentino wrote: > I ask to infra to remove yourself. -- Zoran Regvart
Re: Spring and Spring Boot upgrades
Hi Cameleers, the release notes mention that the deprecated methods were removed in 2.1[1], I don't recall seeing that we use any of those. So other than the change when loading configurations via @SpringBootTest I haven't found any other differences, zoran [1] https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.1-Release-Notes On Mon, Nov 5, 2018 at 4:03 PM, Claus Ibsen wrote: > Hi > > Thanks the PR has been merged so Camel 2.23 supports Spring Boot 2.1. > I wonder if on top of your head / anyone else knows if that upgrade > means Spring Boot 2.0.x is not supported / incompatible. > Just in case someone tries to use Camel 2.23 with Spring Boot 2.0.x. > > And if we know this ahead of time we can write it on the release notes > that its SB 2.1+ etc. > > On Tue, Oct 30, 2018 at 4:19 PM Zoran Regvart wrote: > > > > Hi Cameleers, > > I've tinkered with Spring (5.1.2) and Spring Boot (2.1.0) upgrades, > > any comments welcome: > > > > https://github.com/apache/camel/pull/2584 > > > > zoran > > -- > > Zoran Regvart > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Zoran Regvart
RE: Warning from dev@camel.apache.org
This is the email a find in the header of all the last 2 emails I received dev-return-51928-maroussil=tec-connectivia@camel.apache.org dev-return-51927-maroussil=tec-connectivia@camel.apache.org From: dev-h...@camel.apache.org [dev-h...@camel.apache.org] Sent: Sunday, November 04, 2018 9:34 AM To: Marc-André Roussil Subject: Warning from dev@camel.apache.org Hi! This is the ezmlm program. I'm managing the dev@camel.apache.org mailing list. I'm working for my owner, who can be reached at dev-ow...@camel.apache.org. Messages to you from the dev mailing list seem to have been bouncing. I've attached a copy of the first bounce message I received. If this message bounces too, I will send you a probe. If the probe bounces, I will remove your address from the dev mailing list, without further notice. I've kept a list of which messages from the dev mailing list have bounced from your address. Copies of these messages may be in the archive. To retrieve a set of messages 123-145 (a maximum of 100 per request), send a short message to: To receive a subject and author list for the last 100 or so messages, send a short message to: Here are the message numbers: 51837 51835 51894 51891 --- Enclosed is a copy of the bounce message I received. Return-Path: <> Received: (qmail 97886 invoked for bounce); 24 Oct 2018 19:02:02 - Date: 24 Oct 2018 19:02:02 - From: mailer-dae...@apache.org To: dev-return-518...@camel.apache.org Subject: failure notice
[GitHub] lburgazzoli closed pull request #203: Added some traits and full refactoring
lburgazzoli closed pull request #203: Added some traits and full refactoring URL: https://github.com/apache/camel-k/pull/203 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/deploy/cr-example.yaml b/deploy/cr-example.yaml index c2851c75..253c4026 100644 --- a/deploy/cr-example.yaml +++ b/deploy/cr-example.yaml @@ -3,8 +3,6 @@ kind: Integration metadata: name: example spec: - dependencies: -- camel:groovy source: content: |- // This is Camel K Groovy example route diff --git a/deploy/operator-role-kubernetes.yaml b/deploy/operator-role-kubernetes.yaml index d3865a88..c0c08cba 100644 --- a/deploy/operator-role-kubernetes.yaml +++ b/deploy/operator-role-kubernetes.yaml @@ -61,3 +61,16 @@ rules: - get - list - watch +- apiGroups: + - extensions + resources: + - ingresses + verbs: + - create + - delete + - deletecollection + - get + - list + - patch + - update + - watch diff --git a/deploy/operator-role-openshift.yaml b/deploy/operator-role-openshift.yaml index 788a7ccf..41a5f724 100644 --- a/deploy/operator-role-openshift.yaml +++ b/deploy/operator-role-openshift.yaml @@ -119,3 +119,11 @@ rules: - patch - update - watch +- apiGroups: + - "" + - route.openshift.io + resources: + - routes/custom-host + verbs: + - create + diff --git a/deploy/resources.go b/deploy/resources.go index f370a581..de96acf6 100644 --- a/deploy/resources.go +++ b/deploy/resources.go @@ -2188,8 +2188,6 @@ kind: Integration metadata: name: example spec: - dependencies: -- camel:groovy source: content: |- // This is Camel K Groovy example route @@ -2373,6 +2371,19 @@ rules: - get - list - watch +- apiGroups: + - extensions + resources: + - ingresses + verbs: + - create + - delete + - deletecollection + - get + - list + - patch + - update + - watch ` Resources["operator-role-openshift.yaml"] = @@ -2498,6 +2509,14 @@ rules: - patch - update - watch +- apiGroups: + - "" + - route.openshift.io + resources: + - routes/custom-host + verbs: + - create + ` Resources["operator-service-account.yaml"] = diff --git a/docs/traits.adoc b/docs/traits.adoc index c5ada797..27f90b2c 100644 --- a/docs/traits.adoc +++ b/docs/traits.adoc @@ -23,6 +23,10 @@ The flag `--trait` can be also abbreviated with `-t`. The `enabled` property is available on all traits and can be used to enable/disable them. All traits have their own internal logic to determine if they need to be enabled when the user does not activate them explicitly. +All traits share also a `auto` property that can be used to enable/disable auto-configuration of the trait based on the +environment. The auto-configuration mechanism is able to enable/disable the trait when the `enabled` property is not explicitly +set by the user and also change the trait configuration. The `auto` property is enabled by default. + NOTE: Some traits are applicable only to specific platforms (see "profiles" in the table). A trait may have additional properties that can be configured by the end user. @@ -51,6 +55,13 @@ The following is a list of common traits that can be configured by the end users |=== | Trait | Profiles| Description +| dependencies +| Kubernetes, OpenShift +| Automatically adds dependencies required by the Camel routes by inspecting the user code. + + + + + It's enabled by default. + | service | Kubernetes, OpenShift | Exposes the integration with a Service resource so that it can be accessed by other applications (or integrations) in the same namespace. @@ -73,6 +84,29 @@ The following is a list of common traits that can be configured by the end users + It's enabled by default whenever a Service is added to the integration (through the `service` trait). +[cols="m,"] +!=== + +! route.host +! To configure the host exposed by the route. + +!=== + +| ingress +| Kubernetes +| Exposes the service associated with the integration to the outside world with a Kubernetes Ingress. + + + + + It's enabled by default whenever a Service is added to the integration (through the `service` trait). + +[cols="m,"] +!=== + +! ingress.host +! **Required**. To configure the host exposed by the ingress. + +!=== + |=== @@ -83,6 +117,6 @@ There are also platform traits that **normally should not be configured** by the [options="header",cols="m,,"] |=== | Trait | Profiles| Description -| base | Kubernetes, OpenShift| Creates the basic Kubernetes resource needed for running the integration. +| deployment | Kubernetes, OpenShift | Creates the basic
[GitHub] nicolaferraro opened a new pull request #203: Added some traits and full refactoring
nicolaferraro opened a new pull request #203: Added some traits and full refactoring URL: https://github.com/apache/camel-k/pull/203 Other than adding a `ingress ' trait for Kubernetes and refactoring the dependency discovery mechanism into its own trait, this prepares the work for Knative.. This is an automated message from the Apache Git Service. To respond to the message, please log on 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: Spring and Spring Boot upgrades
FWIW I'm currently using camel 2.22.1 with boot 2.1 without any problems Den man. 5. nov. 2018, 16:04 skrev Claus Ibsen : > Hi > > Thanks the PR has been merged so Camel 2.23 supports Spring Boot 2.1. > I wonder if on top of your head / anyone else knows if that upgrade > means Spring Boot 2.0.x is not supported / incompatible. > Just in case someone tries to use Camel 2.23 with Spring Boot 2.0.x. > > And if we know this ahead of time we can write it on the release notes > that its SB 2.1+ etc. > > On Tue, Oct 30, 2018 at 4:19 PM Zoran Regvart wrote: > > > > Hi Cameleers, > > I've tinkered with Spring (5.1.2) and Spring Boot (2.1.0) upgrades, > > any comments welcome: > > > > https://github.com/apache/camel/pull/2584 > > > > zoran > > -- > > Zoran Regvart > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: Spring and Spring Boot upgrades
Hi Thanks the PR has been merged so Camel 2.23 supports Spring Boot 2.1. I wonder if on top of your head / anyone else knows if that upgrade means Spring Boot 2.0.x is not supported / incompatible. Just in case someone tries to use Camel 2.23 with Spring Boot 2.0.x. And if we know this ahead of time we can write it on the release notes that its SB 2.1+ etc. On Tue, Oct 30, 2018 at 4:19 PM Zoran Regvart wrote: > > Hi Cameleers, > I've tinkered with Spring (5.1.2) and Spring Boot (2.1.0) upgrades, > any comments welcome: > > https://github.com/apache/camel/pull/2584 > > zoran > -- > Zoran Regvart -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: UNSUBSCRIBE ME
I ask to infra to remove yourself. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Monday, November 5, 2018, 3:41:18 PM GMT+1, Marc-André Roussil wrote: I try several times to unsubscribe from your email. Dont send me back this url http://camel.apache.org/mailing-lists.htmlhttp://camel.apache.org/mailing-lists.html UNSUBSCRIBE ME Thanks
UNSUBSCRIBE ME
I try several times to unsubscribe from your email. Dont send me back this url http://camel.apache.org/mailing-lists.htmlhttp://camel.apache.org/mailing-lists.html UNSUBSCRIBE ME Thanks
[GitHub] nicolaferraro closed pull request #202: Fix compatibility with operator sdk 0.0.7
nicolaferraro closed pull request #202: Fix compatibility with operator sdk 0.0.7 URL: https://github.com/apache/camel-k/pull/202 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/.gitignore b/.gitignore index 10611df8..871a20b8 100644 --- a/.gitignore +++ b/.gitignore @@ -1,5 +1,5 @@ # Binary files -/camel-k-operator +/camel-k /kamel # Released Packages diff --git a/build/Makefile b/build/Makefile index f087869b..bfd12c1f 100644 --- a/build/Makefile +++ b/build/Makefile @@ -3,7 +3,7 @@ build: build-runtime build-operator build-kamel build-compile-integration-tests build-go: build-embed-resources build-operator build-kamel build-operator: build-embed-resources - go build -o camel-k-operator ./cmd/camel-k-operator/*.go + go build -o camel-k ./cmd/camel-k/*.go build-kamel: go build -o kamel ./cmd/kamel/*.go @@ -42,7 +42,7 @@ generate: clean: ./mvnw clean -f ./runtime/pom.xml go clean - rm -f camel-k-operator + rm -f camel-k rm -f kamel rm -rf tmp/_maven_output diff --git a/build/travis_build.sh b/build/travis_build.sh index 83e5d127..e7897b4e 100755 --- a/build/travis_build.sh +++ b/build/travis_build.sh @@ -56,7 +56,7 @@ echo "Adding maven artifacts to the image context" echo "Copying binary file to docker dir" mkdir -p ./tmp/_output/bin -cp ./camel-k-operator ./tmp/_output/bin/ +cp ./camel-k ./tmp/_output/bin/ echo "Building the images" export IMAGE=docker.io/apache/camel-k:$(./build/get_version.sh) diff --git a/cmd/camel-k-operator/camel_k_operator.go b/cmd/camel-k/main.go similarity index 100% rename from cmd/camel-k-operator/camel_k_operator.go rename to cmd/camel-k/main.go diff --git a/cmd/kamel/kamel.go b/cmd/kamel/main.go similarity index 100% rename from cmd/kamel/kamel.go rename to cmd/kamel/main.go diff --git a/config/config.yaml b/config/config.yaml index 71ecb897..45de9133 100644 --- a/config/config.yaml +++ b/config/config.yaml @@ -1,3 +1,3 @@ apiVersion: camel.apache.org/v1alpha1 kind: Integration -projectName: camel-k-operator +projectName: camel-k diff --git a/deploy/operator-deployment-kubernetes.yaml b/deploy/operator-deployment-kubernetes.yaml index 608f596f..c41f155b 100644 --- a/deploy/operator-deployment-kubernetes.yaml +++ b/deploy/operator-deployment-kubernetes.yaml @@ -24,7 +24,7 @@ spec: - containerPort: 6 name: metrics command: - - camel-k-operator + - camel-k imagePullPolicy: IfNotPresent env: - name: WATCH_NAMESPACE @@ -32,7 +32,7 @@ spec: fieldRef: fieldPath: metadata.namespace - name: OPERATOR_NAME - value: "camel-k-operator" + value: "camel-k" volumeMounts: - mountPath: /workspace name: camel-k-builder diff --git a/deploy/operator-deployment-openshift.yaml b/deploy/operator-deployment-openshift.yaml index 58cea8a6..da0a9018 100644 --- a/deploy/operator-deployment-openshift.yaml +++ b/deploy/operator-deployment-openshift.yaml @@ -24,7 +24,7 @@ spec: - containerPort: 6 name: metrics command: - - camel-k-operator + - camel-k imagePullPolicy: IfNotPresent env: - name: WATCH_NAMESPACE @@ -32,4 +32,4 @@ spec: fieldRef: fieldPath: metadata.namespace - name: OPERATOR_NAME - value: "camel-k-operator" + value: "camel-k" diff --git a/deploy/resources.go b/deploy/resources.go index a00e23ca..f370a581 100644 --- a/deploy/resources.go +++ b/deploy/resources.go @@ -2234,7 +2234,7 @@ spec: - containerPort: 6 name: metrics command: - - camel-k-operator + - camel-k imagePullPolicy: IfNotPresent env: - name: WATCH_NAMESPACE @@ -2242,7 +2242,7 @@ spec: fieldRef: fieldPath: metadata.namespace - name: OPERATOR_NAME - value: "camel-k-operator" + value: "camel-k" volumeMounts: - mountPath: /workspace name: camel-k-builder @@ -2280,7 +2280,7 @@ spec: - containerPort: 6 name: metrics command: - - camel-k-operator + - camel-k imagePullPolicy: IfNotPresent env: - name: WATCH_NAMESPACE @@ -2288,7 +2288,7 @@ spec: fieldRef: fieldPath: metadata.namespace - name: OPERATOR_NAME - value: "camel-k-operator" + value: "camel-k" `
Re: [VOTE] Release Apache Camel 2.22.2
+1 from wildfly-camel cheers — thomas > On Nov 2, 2018, at 8:27 PM, Alex Dettinger wrote: > > +1 (non-binding) > Nice cut Gregor. > > Alex > > On Fri, Nov 2, 2018 at 1:43 PM Luca Burgazzoli > wrote: > >> +1 (binding) >> >> --- >> Luca Burgazzoli >> >> On Fri, Nov 2, 2018 at 1:31 PM Nicola Ferraro >> wrote: >>> >>> +1 (binding) >>> >>> Thanks! >>> >>> On Fri, Nov 2, 2018 at 10:38 AM Francois Papon < >> francois.pa...@openobject.fr> >>> wrote: >>> +1 (non-binding) Thanks for the release! regards, François Papon fpa...@apache.org Le 02/11/2018 à 10:23, Gregor Zurowski a écrit : > Hi Everyone: > > This is a vote to release Apache Camel 2.22.2, a patch release for >> the > camel-2.22.x branch with 37 improvements and bug fixes. > > Release notes: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344006=12311211 > > Staging repository: > >> https://repository.apache.org/content/repositories/orgapachecamel-1113/ > > Tarballs: >> https://repository.apache.org/content/repositories/orgapachecamel-1113/org/apache/camel/apache-camel/2.22.2/ > > Tag: >> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.22.2 > > Please test this release candidate and cast your vote. > [ ] +1 Release the binary as Apache Camel 2.22.2 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor >>
