GitHub user ramu11 opened a pull request:
https://github.com/apache/camel/pull/2308
CAMEL-12442:rest-dsl - Rest producer should use RestConfiguration
CAMEL-12442:rest-dsl - Rest producer should use RestConfiguration
You can merge this pull request into a Git repository by running:
+1 to move forward publishing the new website.
Regards
JB
Le 25 avr. 2018 à 20:46, à 20:46, Willem Jiang a écrit:
>+1 for bring a new website.
>
>Normally, there are some building blocks project in the github for the
>personal website.
>Last year we built a new website[1] for the ServiceComb p
GitHub user igarashitm opened a pull request:
https://github.com/apache/camel/pull/2307
CAMEL-12460 Fix camel actuator endpoints to get it working with SB2
Also extracted CamelRoutesEndpointProperties as a separated class from
CamelRoutesEndpoint
I wanted to make sure if it
Hi Tomo,
Thank you for sharing that. I see asciidoctor (!= asciidoc) tooling as
a good way to generate reference guides, not that good of a way to
generate the whole static site. I think that's the reasoning why
asciidoctor.org is using Awestruct.
zoran
On Wed, Apr 25, 2018 at 10:49 PM, Tomohisa
Hi,
Wasn't asciidoctor-maven-plugin an option? We're using it to generate AtlasMap
developer guide on each master build.
https://github.com/atlasmap/atlasmap/blob/dc9cceb7e7438b88e5d761b636f2f31f4d5c36ff/docs/pom.xml#L50-L71
https://docs.atlasmap.io/
Thanks,
Tomo
On Wed, 2018-04-25 at 21:55 +02
Hi Cameleers,
On Wed, Apr 25, 2018 at 8:33 PM, Claus Ibsen wrote:
> We are using ascii doc but it should be similar.
Just to chime in, because we use asciidoc, and just to be sure I'm not
questioning that decision it's clearly superior choice vs markdown,
the current stack we have on the website
GitHub user mchandwani opened a pull request:
https://github.com/apache/camel/pull/2306
Fixed the Defect manual commit not working
partitionLastOffset value always remains -1 so consumer.commitSync is never
called in method commitOffset
You can merge this pull request into a Git re
Hi Willem
Great to hear you got some experience with building a website with
markdown content.
We are using ascii doc but it should be similar.
If you wanted to refer to a link in [1] then I dont see that in your email.
On Wed, Apr 25, 2018 at 6:45 PM, Willem Jiang wrote:
> +1 for bring a new
GitHub user PascalSchumacher opened a pull request:
https://github.com/apache/camel/pull/2305
Remove Metric 3.0.1 related classloader leak warning, now that we useâ¦
⦠Metrics 3.2.6.
I guess probably referred to
https://github.com/dropwizard/metrics/issues/742 which was
+1
Great feature, it reminds me an issue years ago where I found a management
context with tons of file endpoint mbeans.
It makes me wonder if the file component would be a good candidate for this
optimisation ?
Alex
On Tue, Apr 24, 2018 at 12:30 PM, Claus Ibsen wrote:
> On Tue, Apr 24, 2018 a
+1 for bring a new website.
Normally, there are some building blocks project in the github for the
personal website.
Last year we built a new website[1] for the ServiceComb project by using
markdown as the content.
Maybe we can do the same thing for the new camel website.
Any thoughts?
Willem J
11 matches
Mail list logo
