Re: [CAMEL 3] Moving sandbox/camel-3.x to master
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: @oscerd2Github: oscerd On Tuesday, December 18, 2018, 9:09:11 AM GMT+1, Zoran Regvart wrote: 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 this work for all? Thoughts? +1 thank you Andrea :) zoran -- Zoran Regvart
Re: [CAMEL 3] Creating 2.x and move sandbox/camel-3.x to master
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 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: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd
[CAMEL 3] Creating 2.x and move sandbox/camel-3.x to master
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: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd
[GitHub] crystaldust opened a new issue #306: The kaniko build pod failed to start
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
$ kubectl logs camel-k-kotlin
Error: please provide a valid path to a Dockerfile within the build context
with --dockerfile
Usage:
executor [flags]
..
```
I've checked the PersistentVolume and find that the /workspace dir is empty,
seems like that the context dir('/workspace/builder-/package/context') is
not created. Any ideas on this?
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: Camel website
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 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 but I keep it in > mind ;) > >> > >> Regards, > >> > >> François Papon > >> fpa...@apache.org > >> > >> Le 17/12/2018 à 12:41, Andrea Cosentino a écrit : > >>> Really nice! Only that problem on mobile, but it looks great. > >>> > >>> -- > >>> Andrea Cosentino > >>> -- > >>> Apache Camel PMC Chair > >>> Apache Karaf Committer > >>> Apache Servicemix PMC Member > >>> Email: ancosen1...@yahoo.com > >>> Twitter: @oscerd2 > >>> Github: oscerd > >>> > >>> > >>> > >>> > >>> > >>> > >>> On Monday, December 17, 2018, 9:33:21 AM GMT+1, Onder SEZGIN < > ond...@apache.org> wrote: > >>> > >>> > >>> > >>> > >>> > >>> Thanks François. It looks very nice. > >>> One minor comment: > >>> Look and feel is overlapping on mobile view. Maybe it could be > adjusted to > >>> be more responsive. > >>> > >>> On Sun, Dec 16, 2018 at 3:59 PM Zoran Regvart > wrote: > >>> > Hi François, > I think that's awesome! Please do create a PR :) > > zoran > On Sat, Dec 15, 2018 at 7:28 PM Francois Papon > wrote: > > Hi guys, > > > > I made some design integration on the website based on the new logo, > > it's not fully finished and it's just a proposal. > > > > You can have a preview about the home page here : > > > > https://openobject.fr/camel/ > > > > If you like it I'm ready to push my PR and move forward with the > > documentation theme ;) > > > > Regards, > > > > François Papon > > fpa...@apache.org > > > > Le 14/12/2018 à 18:03, Claus Ibsen a écrit : > >> Hi > >> > >> Yay its good to see progress on this, and that we can easily have a > >> sneak-peak by browsing that staging site. > >> > >> Great work guys, love to see the collaboration going on, to > >> reinvigorate the Camel project and its website. > >> > >> > >> On Thu, Dec 13, 2018 at 12:36 PM Zoran Regvart > wrote: > >>> Hi Cameleers, > >>> the first iteration of the build[1] of the new website is up on the > staging URL: > >>> https://camel.apache.org/staging/ > >>> > >>> it took a while to get all the kinks worked out but it seems OK > now. > >>> > >>> Bare in mind that this is still very early, rough version: links > will > >>> be broken or point to wrong places, layout and styling is almost > >>> non-existant. > >>> > >>> This at least gives us the opportunity to see any changes we make > >>> really quickly online. > >>> > >>> I'll work on adding some READMEs to explain how to contribute and > >>> cleanup JIRA issues around the new website next. > >>> > >>> zoran > >>> > >>> [1] > > https://builds.apache.org/blue/organizations/jenkins/Camel.website/activity > >>> -- > >>> Zoran Regvart > -- > Zoran Regvart > > > > > >
Re: Release last Camel 2.21.4 release
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 Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Tuesday, December 18, 2018, 1:59:45 PM GMT+1, Claus Ibsen < > claus.ib...@gmail.com> wrote: > > > > > > 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: https://www.manning.com/ibsen2 >
[GitHub] nicolaferraro opened a new issue #305: Allow to customize integration service account
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 `serviceAccountName` field in the integration spec. 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
[GitHub] lburgazzoli opened a new pull request #304: Display relevant custom columns
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, 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
[GitHub] lburgazzoli edited a comment on issue #300: add resources to an integration
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 to be smart. In this case is not so smart :) as it simply check for the presence of a file on the file system, in the class-path and finally it checks the env, but it works. Maybe we can introduce the "platform" protocol also in Apache Camel and have a way to configure what real protocol(s) it has to use under the hoods. I think that lot of thing we be moved in standard Camel utilities once the camel-k runtime will be moved to Apache Camel. 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
[GitHub] lburgazzoli edited a comment on issue #300: add resources to an integration
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 to be smart. In this case is not so smart :) as it simply check for the presence of a file on the file system, in the class-path and finally it checks the env, but it works. Maybe we can introduce the "platform" protocol also in Apache Camel and have a way to configure what real protocol(s) it has to use under the hoods. I think that lot of thing will be moved in standard Camel utilities once the camel-k runtime will be moved to Apache Camel. 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
[GitHub] lburgazzoli edited a comment on issue #300: add resources to an integration
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 to be smart. In this case is not so smart :) as it simply check for the presence of a file on the file system, in the class-path and finally it checks the env, but it works. Maybe we can introduce the "platform" protocol also in Apache Camel and have a way to configure what real protocol(s) it has to use under the hoods. 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
[GitHub] lburgazzoli commented on issue #300: add resources to an integration
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 smart. In this case is not so smart :) as it simply check for the presence of a file on the file system, in the class-path and finally it checks the env, but it works. Maybe we can introduce the "platform" protocol also upstream and have a way to configure what real protocol(s) it has to use under the hoods. 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
[GitHub] davsclaus commented on issue #300: add resources to an integration
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_ (fingers crossed). 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
[GitHub] lburgazzoli commented on issue #300: add resources to an integration
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
from('timer:resources')
.routeId('resources')
.setBody()
.simple("resource:platform:resources-data.txt")
.log('file content is: ${body}')
```
do you mind having a look ?
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
[GitHub] davsclaus commented on issue #249: Add support for template endpoint
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 users or customers and something didn't work, and we needed to bootup their routes. So we needed to stub out their own components, or irrelevant Camel components etc. So stub was faster to add than to replace all of these uris with seda etc. 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
[GitHub] lburgazzoli commented on issue #303: catalog : include camel-k components
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 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
[GitHub] nicolaferraro commented on issue #249: Add support for template endpoint
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. 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
[GitHub] davsclaus commented on issue #249: Add support for template endpoint
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 the knative Camel endpoint, but just _stub it out_. The fact that stub uses an internal VM queue under the hood is a bit of purpose, in case you stub out endpoints that was intended to be bridged. So yeah in this example with sink/source you can say from timer foo to template bar from template bar to log info But they have to run in the same Camel JVM to bridge them together. Don't you want template to create the actual endpoint, eg knative in this example? 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: Release last Camel 2.21.4 release
+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 GMT+1, Claus Ibsen wrote: 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: https://www.manning.com/ibsen2
[GitHub] nicolaferraro commented on issue #249: Add support for template endpoint
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: https://github.com/apache/camel/blob/master/camel-core/src/main/docs/stub-component.adoc Wdyt? 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
Release last Camel 2.21.4 release
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: https://www.manning.com/ibsen2
[GitHub] davsclaus commented on issue #302: catalog should be available as cutom resource
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. 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
[GitHub] davsclaus commented on issue #303: catalog : include camel-k components
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 thus in the standard catalog. 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
[GitHub] davsclaus commented on issue #249: Add support for template endpoint
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 it allows us to change its implementation with more ease and if down the road it turns out it was not as a good idea as we thought, then we can easier deprecate/remote the component and make a better new solution. 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
[GitHub] davsclaus commented on issue #249: Add support for template endpoint
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 concrete endpoint. How this is mapped can be implementation specific in the template component, so it can support looking up via ENV variables, property placeholders, load from resource file etc. 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: Camel website
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 :) > > 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 but I keep it in mind ;) >> >> Regards, >> >> François Papon >> fpa...@apache.org >> >> Le 17/12/2018 à 12:41, Andrea Cosentino a écrit : >>> Really nice! Only that problem on mobile, but it looks great. >>> >>> -- >>> Andrea Cosentino >>> -- >>> Apache Camel PMC Chair >>> Apache Karaf Committer >>> Apache Servicemix PMC Member >>> Email: ancosen1...@yahoo.com >>> Twitter: @oscerd2 >>> Github: oscerd >>> >>> >>> >>> >>> >>> >>> On Monday, December 17, 2018, 9:33:21 AM GMT+1, Onder SEZGIN >>> wrote: >>> >>> >>> >>> >>> >>> Thanks François. It looks very nice. >>> One minor comment: >>> Look and feel is overlapping on mobile view. Maybe it could be adjusted to >>> be more responsive. >>> >>> On Sun, Dec 16, 2018 at 3:59 PM Zoran Regvart wrote: >>> Hi François, I think that's awesome! Please do create a PR :) zoran On Sat, Dec 15, 2018 at 7:28 PM Francois Papon wrote: > Hi guys, > > I made some design integration on the website based on the new logo, > it's not fully finished and it's just a proposal. > > You can have a preview about the home page here : > > https://openobject.fr/camel/ > > If you like it I'm ready to push my PR and move forward with the > documentation theme ;) > > Regards, > > François Papon > fpa...@apache.org > > Le 14/12/2018 à 18:03, Claus Ibsen a écrit : >> Hi >> >> Yay its good to see progress on this, and that we can easily have a >> sneak-peak by browsing that staging site. >> >> Great work guys, love to see the collaboration going on, to >> reinvigorate the Camel project and its website. >> >> >> On Thu, Dec 13, 2018 at 12:36 PM Zoran Regvart wrote: >>> Hi Cameleers, >>> the first iteration of the build[1] of the new website is up on the staging URL: >>> https://camel.apache.org/staging/ >>> >>> it took a while to get all the kinks worked out but it seems OK now. >>> >>> Bare in mind that this is still very early, rough version: links will >>> be broken or point to wrong places, layout and styling is almost >>> non-existant. >>> >>> This at least gives us the opportunity to see any changes we make >>> really quickly online. >>> >>> I'll work on adding some READMEs to explain how to contribute and >>> cleanup JIRA issues around the new website next. >>> >>> zoran >>> >>> [1] https://builds.apache.org/blue/organizations/jenkins/Camel.website/activity >>> -- >>> Zoran Regvart -- Zoran Regvart > >
Re: Camel website
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 but I keep it in mind ;) > > Regards, > > François Papon > fpa...@apache.org > > Le 17/12/2018 à 12:41, Andrea Cosentino a écrit : > > Really nice! Only that problem on mobile, but it looks great. > > > > -- > > Andrea Cosentino > > -- > > Apache Camel PMC Chair > > Apache Karaf Committer > > Apache Servicemix PMC Member > > Email: ancosen1...@yahoo.com > > Twitter: @oscerd2 > > Github: oscerd > > > > > > > > > > > > > > On Monday, December 17, 2018, 9:33:21 AM GMT+1, Onder SEZGIN > > wrote: > > > > > > > > > > > > Thanks François. It looks very nice. > > One minor comment: > > Look and feel is overlapping on mobile view. Maybe it could be adjusted to > > be more responsive. > > > > On Sun, Dec 16, 2018 at 3:59 PM Zoran Regvart wrote: > > > >> Hi François, > >> I think that's awesome! Please do create a PR :) > >> > >> zoran > >> On Sat, Dec 15, 2018 at 7:28 PM Francois Papon > >> wrote: > >>> Hi guys, > >>> > >>> I made some design integration on the website based on the new logo, > >>> it's not fully finished and it's just a proposal. > >>> > >>> You can have a preview about the home page here : > >>> > >>> https://openobject.fr/camel/ > >>> > >>> If you like it I'm ready to push my PR and move forward with the > >>> documentation theme ;) > >>> > >>> Regards, > >>> > >>> François Papon > >>> fpa...@apache.org > >>> > >>> Le 14/12/2018 à 18:03, Claus Ibsen a écrit : > Hi > > Yay its good to see progress on this, and that we can easily have a > sneak-peak by browsing that staging site. > > Great work guys, love to see the collaboration going on, to > reinvigorate the Camel project and its website. > > > On Thu, Dec 13, 2018 at 12:36 PM Zoran Regvart > >> wrote: > > Hi Cameleers, > > the first iteration of the build[1] of the new website is up on the > >> staging URL: > > https://camel.apache.org/staging/ > > > > it took a while to get all the kinks worked out but it seems OK now. > > > > Bare in mind that this is still very early, rough version: links will > > be broken or point to wrong places, layout and styling is almost > > non-existant. > > > > This at least gives us the opportunity to see any changes we make > > really quickly online. > > > > I'll work on adding some READMEs to explain how to contribute and > > cleanup JIRA issues around the new website next. > > > > zoran > > > > [1] > >> https://builds.apache.org/blue/organizations/jenkins/Camel.website/activity > > -- > > Zoran Regvart > > >> > >> -- > >> Zoran Regvart > >> -- Zoran Regvart
[GitHub] zregvart closed pull request #3: [CAMEL-12998] Website design proposal
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 request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/antora-ui-camel/src/css/base.css b/antora-ui-camel/src/css/base.css
index 35391f8..6eae566 100644
--- a/antora-ui-camel/src/css/base.css
+++ b/antora-ui-camel/src/css/base.css
@@ -1,8 +1,9 @@
:root {
- --color-text: #222;
- --color-navbar-bg: #0a0a0a;
- --color-navbar-bg-focus: #000;
- --color-navbar-text: #fff;
+ --color-text: #000;
+ --color-navbar-bg: #fff;
+ --color-navbar-bg-focus: #ed8225;
+ --color-navbar-text: #ed8225;
+ --color-navbar-text-link-hover: #fff;
}
html,
@@ -18,14 +19,15 @@ body {
html {
box-sizing: border-box;
- font-family: "Droid Serif", "DejaVu Serif", serif;
- font-size: 1.1em;
+ font-family: "Open Sans", "DejaVu Serif", serif;
+ font-size: 1em;
text-size-adjust: 100%;
}
@media screen and (min-width: 1024px) {
html {
-font-size: 1.2em;
+font-family: "Open Sans", "DejaVu Serif", serif;
+font-size: 1em;
}
}
@@ -37,10 +39,11 @@ body {
a {
text-decoration: none;
+ color: #ed8225;
}
a:hover {
- text-decoration: underline;
+ text-decoration: none;
}
code,
diff --git a/antora-ui-camel/src/css/footer.css
b/antora-ui-camel/src/css/footer.css
index a0f5cf5..882482a 100644
--- a/antora-ui-camel/src/css/footer.css
+++ b/antora-ui-camel/src/css/footer.css
@@ -1,8 +1,7 @@
footer.footer {
- font-size: 0.85rem;
- background-color: #2c2c2c;
- color: #8e8e8e;
padding: 0.5rem 1rem;
+ min-height: 200px;
+ text-align: center;
}
.footer p {
@@ -10,5 +9,5 @@ footer.footer {
}
.footer a {
- color: #5d5d5d;
+ color: #ed8225;
}
diff --git a/antora-ui-camel/src/css/header.css
b/antora-ui-camel/src/css/header.css
index 0bb4ec0..54eb698 100644
--- a/antora-ui-camel/src/css/header.css
+++ b/antora-ui-camel/src/css/header.css
@@ -1,5 +1,5 @@
:root {
- --navbar-height: 3.25rem;
+ --navbar-height: 4.25rem;
}
html.is-clipped--navbar {
@@ -13,7 +13,7 @@ body {
.navbar {
background-color: var(--color-navbar-bg);
color: var(--color-navbar-text);
- font-size: 0.8rem;
+ font-size: 1rem;
height: var(--navbar-height);
position: fixed;
top: 0;
@@ -30,6 +30,7 @@ body {
.navbar-brand .navbar-item:first-child a {
color: var(--color-navbar-text);
font-size: 1.15rem;
+ width: 180px;
}
.navbar-brand .separator {
@@ -45,7 +46,7 @@ body {
.navbar-end > a.navbar-item:hover,
.navbar-end .navbar-link:hover {
background-color: var(--color-navbar-bg-focus);
-color: var(--color-navbar-text);
+color: var(--color-navbar-text-link-hover);
}
.navbar-end .navbar-link::after {
@@ -54,7 +55,7 @@ body {
.navbar-item.has-dropdown:hover .navbar-link {
background-color: var(--color-navbar-bg-focus);
-color: var(--color-navbar-text);
+color: var(--color-navbar-text-link-hover);
}
}
@@ -63,6 +64,12 @@ body {
display: flex;
flex-shrink: 0;
height: var(--navbar-height);
+ background-image: url('../img/logo-camel-medium.png');
+ background-repeat: no-repeat;
+ background-size: 160px;
+ background-position-x: 10px;
+ background-position-y: 10px;
+ width: 180px;
}
.navbar-burger {
diff --git a/antora-ui-camel/src/css/main.css b/antora-ui-camel/src/css/main.css
index facfd77..a335978 100644
--- a/antora-ui-camel/src/css/main.css
+++ b/antora-ui-camel/src/css/main.css
@@ -9,3 +9,220 @@
min-width: 0;
}
}
+
+.container {
+ margin: 0 auto;
+ position: relative;
+ padding-bottom: 50px;
+}
+
+.centered {
+ max-width: 500px;
+ margin: 0 auto;
+ text-align: center;
+}
+
+@media screen and (min-width: 1088px) {
+ .container {
+max-width: 960px;
+width: 960px;
+ }
+}
+
+@media screen and (min-width: 1280px) {
+ .container {
+max-width: 1152px;
+width: 1152px;
+ }
+}
+
+.full-height {
+ min-height: 100vh;
+}
+
+.bg-grey {
+ background-color: #fbfbfb;
+}
+
+.bg-orange {
+ background-color: #ed8225;
+}
+
+.bg-brown {
+ background-color: #6c5d53;
+}
+
+.text-white {
+ color: #fff;
+}
+
+.text-orange {
+ color: #ed8225;
+}
+
+.text-brown {
+ color: #6c5d53;
+}
+
+.muted {
+ color: #999;
+}
+
+.title {
+ font-size: 1.85em;
+ padding-top: 50px;
+}
+
+.subtitle {
+ font-size: 1.45em;
+ font-weight: normal;
+}
+
+.logo-big {
+ width: 200px;
+ height: 200px;
+}
+
+.logo-small {
+ width: 100px;
+ height: 100px;
+}
+
+.img-fluid {
+ max-width: 100%;
+ height: auto;
+}
+
+.column.logo {
+ margin-top: 100px;
+}
+
+.columns:not(.is-desktop) {
+ display: flex;
+}
+
+.columns.centered {
+ align-items: center;
+}
+
+.columns:last-child {
+ margin-bottom: -0.75rem;
+}
+
+.columns {
+ margin-left: -0.75rem;
+ margin-right:
[GitHub] fpapon opened a new pull request #3: [CAMEL-12998] Website design proposal
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 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
[GitHub] lburgazzoli commented on issue #300: add resources to an integration
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 mechanism so I guess that for knative we should always generate a new container image until they find a solution to inject resources to an image. 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
[GitHub] lburgazzoli opened a new pull request #303: catalog : include camel-k components
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, 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
[GitHub] nicolaferraro commented on a change in pull request #300: add resources to an integration
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 []v1alpha1.Artifact
SelectedArtifacts []v1alpha1.Artifact
Archive string
- ComputeClasspath bool
- MainClass string
+ ContextFiler func(integrationContext *v1alpha1.IntegrationContext)
bool
Review comment:
Typo
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: [CAMEL 3] Moving sandbox/camel-3.x to master
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 this work for all? Thoughts? +1 thank you Andrea :) zoran -- Zoran Regvart
