Re: Hosted web site

2018-10-30 Thread Tadayoshi Sato
Awesome stuff, Zoran!  Thank you.

I'll peek into the asf-site branch and try to polish it.

Best regards,
Tadayoshi

On Tue, Oct 30, 2018 at 10:13 PM Andrea Cosentino
 wrote:

> Great stuff!
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Tuesday, October 30, 2018, 2:05:04 PM GMT+1, Zoran Regvart <
> zo...@regvart.com> wrote:
>
>
>
>
>
> Hi Tadayoshi & Cameleers,
> so the staging site now works* it's at:
>
> https://camel.apache.org/staging/
>
> *and by that I mean: the content of camel-website's asf-site branch is
> published there. It is pretty much broken at the moment, CSS and links
> are generated with absolute values, I need to take a look and make
> them relative so that the website can be nested in that /staging
> directory.
>
> zoran
>
> On Tue, Oct 30, 2018 at 11:40 AM, Zoran Regvart  wrote:
> > Hi Tadayoshi,
> > I'm really sorry I had little time to look into this, the process
> > should look like this:
> >
> > We make changes on the camel.git gitbox repository (or GitHub mirror)
> > to the `website` branch (till it's merged over to `master`), Jenkins
> > builds the website (Jenkinsfile on `website` branch does this[1]) and
> > pushes to the camel-website.git repository's `asf-site` branch. Then a
> > script provided by the INFRA[2] should sync with the website's
> > /staging directory.
> >
> > I think we need a `asf-site-staging` and a `asf-site` branches on
> > `camel-website.git` repository and a way to merge from one repository
> > to the other (Jenkins job?), but let's make some smaller steps first.
> >
> > zoran
> >
> > [1]
> https://gitbox.apache.org/repos/asf?p=camel.git;a=blob;f=Jenkinsfile;h=f094a624332bed955c686ec4a9951aeaa004c258;hb=refs/heads/website#l47
> > [2] https://issues.apache.org/jira/browse/INFRA-15969
> >
> > On Tue, Oct 30, 2018 at 9:59 AM, Tadayoshi Sato
> >  wrote:
> >> Hi all,
> >>
> >> I've been working on migrating docs, and while there are still a number
> of
> >> pages to be migrated yet it's also becoming in good shape. I think it's
> >> good time to host the docs somewhere so that everyone can read and
> further
> >> contribute to the site.
> >>
> >> I'm aware that recently Francois and Zoran worked on doc site generation
> >> and https://github.com/apache/camel-website. Is it currently accessible
> >> online?  Can we publish the static site somewhere like GH Pages,
> surge.sh,
> >> or Netlify?
> >>
> >> The docs are already available on GH as asciidoc but the problem is that
> >> links of reference style i.e. <> do not work on the
> >> plain GH. I believe we need some place where those reference style links
> >> are also rendered.
> >>
> >> Best regards,
> >> Tadayoshi
> >
> >
> >
> > --
> > Zoran Regvart
>
>
>
> --
> Zoran Regvart
>


[GitHub] lburgazzoli opened a new pull request #200: Cannot configure traits

2018-10-30 Thread GitBox
lburgazzoli opened a new pull request #200: Cannot configure traits
URL: https://github.com/apache/camel-k/pull/200
 
 
   Fixes #199


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

2018-10-30 Thread Zoran Regvart
Hi Cameleers,
looks like the build succeeded, but is hanging for some reason (could
be infrastructure related, not sure):

https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/spring-upgrades/1/console

zoran

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



-- 
Zoran Regvart


Re: Spring and Spring Boot upgrades

2018-10-30 Thread Zoran Regvart
Hi David,
you can see it here:

https://gist.github.com/zregvart/0581388eb6021c0b22eaeb5e19150579

I fiddled with configuration classes loaded, but that test really made
no sense to me, it seemed to me that it was exercising
ApplicationContextRunner not something Camel related at all...

zoran

On Tue, Oct 30, 2018 at 8:55 PM, David Karlsen  wrote:
> Do you remember which error message you got with the test?
>
> Den tir. 30. okt. 2018 kl. 16:19 skrev Zoran Regvart :
>
>> 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
>>
>
>
> --
> --
> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen



-- 
Zoran Regvart


Re: Spring and Spring Boot upgrades

2018-10-30 Thread David Karlsen
Do you remember which error message you got with the test?

Den tir. 30. okt. 2018 kl. 16:19 skrev Zoran Regvart :

> 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
>


-- 
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen


Spring and Spring Boot upgrades

2018-10-30 Thread Zoran Regvart
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


[GitHub] nicolaferraro opened a new issue #199: Cannot configure traits

2018-10-30 Thread GitBox
nicolaferraro opened a new issue #199: Cannot configure traits
URL: https://github.com/apache/camel-k/issues/199
 
 
   `kamel run --trait service.enabled=false file.groovy`
   
   Result:
   ```
   Error: service.enabled=false is not a valid trait property
   ```
   
   I wonder if it's not better just to define types as go structs. We don't 
need dynamic unmarshalling. Wdyt @lburgazzoli ?


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: Hosted web site

2018-10-30 Thread Andrea Cosentino
Great stuff!

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Tuesday, October 30, 2018, 2:05:04 PM GMT+1, Zoran Regvart 
 wrote: 





Hi Tadayoshi & Cameleers,
so the staging site now works* it's at:

https://camel.apache.org/staging/

*and by that I mean: the content of camel-website's asf-site branch is
published there. It is pretty much broken at the moment, CSS and links
are generated with absolute values, I need to take a look and make
them relative so that the website can be nested in that /staging
directory.

zoran

On Tue, Oct 30, 2018 at 11:40 AM, Zoran Regvart  wrote:
> Hi Tadayoshi,
> I'm really sorry I had little time to look into this, the process
> should look like this:
>
> We make changes on the camel.git gitbox repository (or GitHub mirror)
> to the `website` branch (till it's merged over to `master`), Jenkins
> builds the website (Jenkinsfile on `website` branch does this[1]) and
> pushes to the camel-website.git repository's `asf-site` branch. Then a
> script provided by the INFRA[2] should sync with the website's
> /staging directory.
>
> I think we need a `asf-site-staging` and a `asf-site` branches on
> `camel-website.git` repository and a way to merge from one repository
> to the other (Jenkins job?), but let's make some smaller steps first.
>
> zoran
>
> [1] 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=blob;f=Jenkinsfile;h=f094a624332bed955c686ec4a9951aeaa004c258;hb=refs/heads/website#l47
> [2] https://issues.apache.org/jira/browse/INFRA-15969
>
> On Tue, Oct 30, 2018 at 9:59 AM, Tadayoshi Sato
>  wrote:
>> Hi all,
>>
>> I've been working on migrating docs, and while there are still a number of
>> pages to be migrated yet it's also becoming in good shape. I think it's
>> good time to host the docs somewhere so that everyone can read and further
>> contribute to the site.
>>
>> I'm aware that recently Francois and Zoran worked on doc site generation
>> and https://github.com/apache/camel-website. Is it currently accessible
>> online?  Can we publish the static site somewhere like GH Pages, surge.sh,
>> or Netlify?
>>
>> The docs are already available on GH as asciidoc but the problem is that
>> links of reference style i.e. <> do not work on the
>> plain GH. I believe we need some place where those reference style links
>> are also rendered.
>>
>> Best regards,
>> Tadayoshi
>
>
>
> --
> Zoran Regvart



-- 
Zoran Regvart


Re: Hosted web site

2018-10-30 Thread Zoran Regvart
Hi Tadayoshi & Cameleers,
so the staging site now works* it's at:

https://camel.apache.org/staging/

*and by that I mean: the content of camel-website's asf-site branch is
published there. It is pretty much broken at the moment, CSS and links
are generated with absolute values, I need to take a look and make
them relative so that the website can be nested in that /staging
directory.

zoran

On Tue, Oct 30, 2018 at 11:40 AM, Zoran Regvart  wrote:
> Hi Tadayoshi,
> I'm really sorry I had little time to look into this, the process
> should look like this:
>
> We make changes on the camel.git gitbox repository (or GitHub mirror)
> to the `website` branch (till it's merged over to `master`), Jenkins
> builds the website (Jenkinsfile on `website` branch does this[1]) and
> pushes to the camel-website.git repository's `asf-site` branch. Then a
> script provided by the INFRA[2] should sync with the website's
> /staging directory.
>
> I think we need a `asf-site-staging` and a `asf-site` branches on
> `camel-website.git` repository and a way to merge from one repository
> to the other (Jenkins job?), but let's make some smaller steps first.
>
> zoran
>
> [1] 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=blob;f=Jenkinsfile;h=f094a624332bed955c686ec4a9951aeaa004c258;hb=refs/heads/website#l47
> [2] https://issues.apache.org/jira/browse/INFRA-15969
>
> On Tue, Oct 30, 2018 at 9:59 AM, Tadayoshi Sato
>  wrote:
>> Hi all,
>>
>> I've been working on migrating docs, and while there are still a number of
>> pages to be migrated yet it's also becoming in good shape. I think it's
>> good time to host the docs somewhere so that everyone can read and further
>> contribute to the site.
>>
>> I'm aware that recently Francois and Zoran worked on doc site generation
>> and https://github.com/apache/camel-website. Is it currently accessible
>> online?  Can we publish the static site somewhere like GH Pages, surge.sh,
>> or Netlify?
>>
>> The docs are already available on GH as asciidoc but the problem is that
>> links of reference style i.e. <> do not work on the
>> plain GH. I believe we need some place where those reference style links
>> are also rendered.
>>
>> Best regards,
>> Tadayoshi
>
>
>
> --
> Zoran Regvart



-- 
Zoran Regvart


[GitHub] shyabithd commented on issue #194: camel-k-context-jvm, camel-k-context-kotlin, camel-k-context-groovy pods goes into error state when installing camel-k

2018-10-30 Thread GitBox
shyabithd commented on issue #194: camel-k-context-jvm, camel-k-context-kotlin, 
camel-k-context-groovy pods goes into error state when installing camel-k
URL: https://github.com/apache/camel-k/issues/194#issuecomment-434273436
 
 
   Thanks @nicolaferraro for the help. I will try 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


[GitHub] nicolaferraro closed pull request #198: (chore) add an example of xml route

2018-10-30 Thread GitBox
nicolaferraro closed pull request #198: (chore) add an example of xml route
URL: https://github.com/apache/camel-k/pull/198
 
 
   

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/runtime/examples/hello.xml b/runtime/examples/hello.xml
new file mode 100644
index ..ff9bc8dc
--- /dev/null
+++ b/runtime/examples/hello.xml
@@ -0,0 +1,28 @@
+
+
+http://www.w3.org/2001/XMLSchema-instance;
+  xmlns="http://camel.apache.org/schema/spring;
+  xsi:schemaLocation="http://camel.apache.org/schema/spring 
http://camel.apache.org/schema/spring/camel-spring.xsd;>
+
+
+
+
+Hello World!!!
+
+
+
+
+
diff --git 
a/runtime/jvm/src/main/java/org/apache/camel/k/jvm/RoutesLoaders.java 
b/runtime/jvm/src/main/java/org/apache/camel/k/jvm/RoutesLoaders.java
index 0ffafbc9..a9ecf609 100644
--- a/runtime/jvm/src/main/java/org/apache/camel/k/jvm/RoutesLoaders.java
+++ b/runtime/jvm/src/main/java/org/apache/camel/k/jvm/RoutesLoaders.java
@@ -163,7 +163,7 @@ public void configure() throws Exception {
 getContext().loadRestsDefinition(is)
 );
 } catch (UnmarshalException e) {
-LOGGER.debug("Unbale to load RestsDefinition: {}", 
e.getMessage());
+LOGGER.debug("Unable to load RestsDefinition: {}", 
e.getMessage());
 }
 }
 }


 


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 opened a new pull request #198: (chore) add an example of xml route

2018-10-30 Thread GitBox
nicolaferraro opened a new pull request #198: (chore) add an example of xml 
route
URL: https://github.com/apache/camel-k/pull/198
 
 
   


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: Hosted web site

2018-10-30 Thread Zoran Regvart
Hi Tadayoshi,
I'm really sorry I had little time to look into this, the process
should look like this:

We make changes on the camel.git gitbox repository (or GitHub mirror)
to the `website` branch (till it's merged over to `master`), Jenkins
builds the website (Jenkinsfile on `website` branch does this[1]) and
pushes to the camel-website.git repository's `asf-site` branch. Then a
script provided by the INFRA[2] should sync with the website's
/staging directory.

I think we need a `asf-site-staging` and a `asf-site` branches on
`camel-website.git` repository and a way to merge from one repository
to the other (Jenkins job?), but let's make some smaller steps first.

zoran

[1] 
https://gitbox.apache.org/repos/asf?p=camel.git;a=blob;f=Jenkinsfile;h=f094a624332bed955c686ec4a9951aeaa004c258;hb=refs/heads/website#l47
[2] https://issues.apache.org/jira/browse/INFRA-15969

On Tue, Oct 30, 2018 at 9:59 AM, Tadayoshi Sato
 wrote:
> Hi all,
>
> I've been working on migrating docs, and while there are still a number of
> pages to be migrated yet it's also becoming in good shape. I think it's
> good time to host the docs somewhere so that everyone can read and further
> contribute to the site.
>
> I'm aware that recently Francois and Zoran worked on doc site generation
> and https://github.com/apache/camel-website. Is it currently accessible
> online?  Can we publish the static site somewhere like GH Pages, surge.sh,
> or Netlify?
>
> The docs are already available on GH as asciidoc but the problem is that
> links of reference style i.e. <> do not work on the
> plain GH. I believe we need some place where those reference style links
> are also rendered.
>
> Best regards,
> Tadayoshi



-- 
Zoran Regvart


[GitHub] nicolaferraro closed pull request #197: Use a working kaniko sha

2018-10-30 Thread GitBox
nicolaferraro closed pull request #197: Use a working kaniko sha
URL: https://github.com/apache/camel-k/pull/197
 
 
   

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/pkg/build/publish/kaniko_publisher.go 
b/pkg/build/publish/kaniko_publisher.go
index b36e867b..ac356eb2 100644
--- a/pkg/build/publish/kaniko_publisher.go
+++ b/pkg/build/publish/kaniko_publisher.go
@@ -122,7 +122,7 @@ func (b *kanikoPublisher) publish(tarFile string, 
baseImageName string, source b
Containers: []v1.Container{
{
Name:  "kaniko",
-   Image: 
"gcr.io/kaniko-project/executor:latest",
+   Image: 
"gcr.io/kaniko-project/executor@sha256:f29393d9c8d40296e1692417089aa2023494bce9afd632acac7dd0aea763e5bc",
Args: []string{
"--dockerfile=Dockerfile",
"--context=" + contextDir,


 


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 #197: Use a working kaniko sha

2018-10-30 Thread GitBox
nicolaferraro commented on issue #197: Use a working kaniko sha
URL: https://github.com/apache/camel-k/pull/197#issuecomment-434245941
 
 
   Need to fix flacky tests...


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 closed issue #194: camel-k-context-jvm, camel-k-context-kotlin, camel-k-context-groovy pods goes into error state when installing camel-k

2018-10-30 Thread GitBox
nicolaferraro closed issue #194: camel-k-context-jvm, camel-k-context-kotlin, 
camel-k-context-groovy pods goes into error state when installing camel-k
URL: https://github.com/apache/camel-k/issues/194
 
 
   


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 #194: camel-k-context-jvm, camel-k-context-kotlin, camel-k-context-groovy pods goes into error state when installing camel-k

2018-10-30 Thread GitBox
nicolaferraro commented on issue #194: camel-k-context-jvm, 
camel-k-context-kotlin, camel-k-context-groovy pods goes into error state when 
installing camel-k
URL: https://github.com/apache/camel-k/issues/194#issuecomment-434238783
 
 
   @shyabithd there's a new version of kaniko released yesterday. I've fixed 
the issue for 0.0.5 onwards, but you should be able to have it working on 0.0.4 
by doing:
   
   ```
   # update the Kaniko image
   eval $(minikube docker-env)
   docker pull gcr.io/kaniko-project/executor:latest
   # reinstall camel k
   kubectl delete integrationplatform camel-k
   kubectl delete delete ictx jvm groovy kotlin
   kamel install
   ```


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 opened a new pull request #197: Use a working kaniko sha

2018-10-30 Thread GitBox
nicolaferraro opened a new pull request #197: Use a working kaniko sha
URL: https://github.com/apache/camel-k/pull/197
 
 
   Fix #194 .
   
   


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 opened a new issue #196: Use Kaniko Cache to speedup

2018-10-30 Thread GitBox
nicolaferraro opened a new issue #196: Use Kaniko Cache to speedup
URL: https://github.com/apache/camel-k/issues/196
 
 
   https://github.com/GoogleContainerTools/kaniko/pull/383/files
   
   It takes quite some time for Kaniko to extract the base image each time it 
needs to do a build. It might be useful to cache the root image in a volume.


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


Hosted web site

2018-10-30 Thread Tadayoshi Sato
Hi all,

I've been working on migrating docs, and while there are still a number of
pages to be migrated yet it's also becoming in good shape. I think it's
good time to host the docs somewhere so that everyone can read and further
contribute to the site.

I'm aware that recently Francois and Zoran worked on doc site generation
and https://github.com/apache/camel-website. Is it currently accessible
online?  Can we publish the static site somewhere like GH Pages, surge.sh,
or Netlify?

The docs are already available on GH as asciidoc but the problem is that
links of reference style i.e. <> do not work on the
plain GH. I believe we need some place where those reference style links
are also rendered.

Best regards,
Tadayoshi


[GitHub] nicolaferraro commented on issue #194: camel-k-context-jvm, camel-k-context-kotlin, camel-k-context-groovy pods goes into error state when installing camel-k

2018-10-30 Thread GitBox
nicolaferraro commented on issue #194: camel-k-context-jvm, 
camel-k-context-kotlin, camel-k-context-groovy pods goes into error state when 
installing camel-k
URL: https://github.com/apache/camel-k/issues/194#issuecomment-434216766
 
 
   This should happen when the connection is slow. It looks that that should be 
fixed now: 
https://github.com/GoogleContainerTools/kaniko/issues/245#issuecomment-428698222.
   
   I'm going to change the kaniko image used under the hood.


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