You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2017/02/04 08:51:36 UTC
The all seeing camel-catalog
Hi
Just wanted to share that we now include every Camel artifact in the
camel-catalog.
What was missing was the other/misc components which is now also included.
So the tables you see at is 100% generated from the catalog
https://github.com/apache/camel/tree/master/components#components
Likewise it keeps the TOC for the (future) website up to date as well et all.
The build is also able to detect if we have missing documentation for
any of these artifacts, and we can therefore better ensure we have
documentation for all of it. And we can keep that documentation with
the source code in the artifact.
That documentation is also included in the catalog, which allows
tooling to access that as well.
The catalog also allows to use runtime providers so you can filter out
what that given runtime supports. For example the karaf runtime
provider will only shown/include what you can use on karaf. Ditto for
spring-boot etc.
And the catalog has a rest api which we could potentially use to build
an interactive website.
https://github.com/apache/camel/tree/master/platforms/catalog-rest-app
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: The all seeing camel-catalog
Posted by Pontus Ullgren <ul...@gmail.com>.
Hi,
A somewhat related question that I have been meaning to ask for a while.
Has there been any thoughts on the documentation for the camel extra
components?
It has previously been hosted on the ASF camel website but from what I can
tell this will no longer be the case after the switch to using the adoc
based documentation. Is this correct?
Thanks
Pontus
On Sat, 4 Feb 2017, 21:33 Claus Ibsen, <cl...@gmail.com> wrote:
> Hi Dmitry
>
> Well spotted. I have just fixed this so its included now.
>
> On Sat, Feb 4, 2017 at 7:12 PM, Dmitry Volodin <dm...@gmail.com> wrote:
> > Hi Claus!
> >
> > Please note, that the camel-olingo2 looks like missing in the readme file
> >
> > Сб, 4 февр. 2017 г. в 11:52, Claus Ibsen <cl...@gmail.com>:
> >
> >> Hi
> >>
> >> Just wanted to share that we now include every Camel artifact in the
> >> camel-catalog.
> >> What was missing was the other/misc components which is now also
> included.
> >>
> >> So the tables you see at is 100% generated from the catalog
> >> https://github.com/apache/camel/tree/master/components#components
> >>
> >> Likewise it keeps the TOC for the (future) website up to date as well et
> >> all.
> >>
> >> The build is also able to detect if we have missing documentation for
> >> any of these artifacts, and we can therefore better ensure we have
> >> documentation for all of it. And we can keep that documentation with
> >> the source code in the artifact.
> >>
> >> That documentation is also included in the catalog, which allows
> >> tooling to access that as well.
> >>
> >> The catalog also allows to use runtime providers so you can filter out
> >> what that given runtime supports. For example the karaf runtime
> >> provider will only shown/include what you can use on karaf. Ditto for
> >> spring-boot etc.
> >>
> >> And the catalog has a rest api which we could potentially use to build
> >> an interactive website.
> >> https://github.com/apache/camel/tree/master/platforms/catalog-rest-app
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> http://davsclaus.com @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
> >>
> > --
> > -- Best regards, Dmitry Volodin
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: The all seeing camel-catalog
Posted by Claus Ibsen <cl...@gmail.com>.
Hi Dmitry
Well spotted. I have just fixed this so its included now.
On Sat, Feb 4, 2017 at 7:12 PM, Dmitry Volodin <dm...@gmail.com> wrote:
> Hi Claus!
>
> Please note, that the camel-olingo2 looks like missing in the readme file
>
> Сб, 4 февр. 2017 г. в 11:52, Claus Ibsen <cl...@gmail.com>:
>
>> Hi
>>
>> Just wanted to share that we now include every Camel artifact in the
>> camel-catalog.
>> What was missing was the other/misc components which is now also included.
>>
>> So the tables you see at is 100% generated from the catalog
>> https://github.com/apache/camel/tree/master/components#components
>>
>> Likewise it keeps the TOC for the (future) website up to date as well et
>> all.
>>
>> The build is also able to detect if we have missing documentation for
>> any of these artifacts, and we can therefore better ensure we have
>> documentation for all of it. And we can keep that documentation with
>> the source code in the artifact.
>>
>> That documentation is also included in the catalog, which allows
>> tooling to access that as well.
>>
>> The catalog also allows to use runtime providers so you can filter out
>> what that given runtime supports. For example the karaf runtime
>> provider will only shown/include what you can use on karaf. Ditto for
>> spring-boot etc.
>>
>> And the catalog has a rest api which we could potentially use to build
>> an interactive website.
>> https://github.com/apache/camel/tree/master/platforms/catalog-rest-app
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>
> --
> -- Best regards, Dmitry Volodin
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: The all seeing camel-catalog
Posted by Dmitry Volodin <dm...@gmail.com>.
Hi Claus!
Please note, that the camel-olingo2 looks like missing in the readme file
Сб, 4 февр. 2017 г. в 11:52, Claus Ibsen <cl...@gmail.com>:
> Hi
>
> Just wanted to share that we now include every Camel artifact in the
> camel-catalog.
> What was missing was the other/misc components which is now also included.
>
> So the tables you see at is 100% generated from the catalog
> https://github.com/apache/camel/tree/master/components#components
>
> Likewise it keeps the TOC for the (future) website up to date as well et
> all.
>
> The build is also able to detect if we have missing documentation for
> any of these artifacts, and we can therefore better ensure we have
> documentation for all of it. And we can keep that documentation with
> the source code in the artifact.
>
> That documentation is also included in the catalog, which allows
> tooling to access that as well.
>
> The catalog also allows to use runtime providers so you can filter out
> what that given runtime supports. For example the karaf runtime
> provider will only shown/include what you can use on karaf. Ditto for
> spring-boot etc.
>
> And the catalog has a rest api which we could potentially use to build
> an interactive website.
> https://github.com/apache/camel/tree/master/platforms/catalog-rest-app
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
--
-- Best regards, Dmitry Volodin
Re: The all seeing camel-catalog
Posted by Babak Vahdat <ba...@swissonline.ch>.
Very nice & awesome!
Babak
> On 04 Feb 2017, at 09:51, Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi
>
> Just wanted to share that we now include every Camel artifact in the
> camel-catalog.
> What was missing was the other/misc components which is now also included.
>
> So the tables you see at is 100% generated from the catalog
> https://github.com/apache/camel/tree/master/components#components
>
> Likewise it keeps the TOC for the (future) website up to date as well et all.
>
> The build is also able to detect if we have missing documentation for
> any of these artifacts, and we can therefore better ensure we have
> documentation for all of it. And we can keep that documentation with
> the source code in the artifact.
>
> That documentation is also included in the catalog, which allows
> tooling to access that as well.
>
> The catalog also allows to use runtime providers so you can filter out
> what that given runtime supports. For example the karaf runtime
> provider will only shown/include what you can use on karaf. Ditto for
> spring-boot etc.
>
> And the catalog has a rest api which we could potentially use to build
> an interactive website.
> https://github.com/apache/camel/tree/master/platforms/catalog-rest-app
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2