I’ve written an asciidoctor extension that queries the Antora content catalog
and constructs simple reports. We might be able to use this to have Antora
generate the index tables in the components component.
The basic idea is to have the documentation generator transfer some information
from
Looks good, many thanks!
A 51 s build is amazing!! I’ll have to see if I can get something close to
that!
David Jencks
> On Apr 6, 2020, at 4:25 AM, Guillaume Nodet wrote:
>
> I think I've fixed the issues.
> David, could you have a look please ?
>
> Le lun. 6 avr. 2020 à 11:58, Guillaume
Camel-bindy was failing for me. Fixed
Il lun 6 apr 2020, 20:50 Pascal Schumacher ha
scritto:
> Yes, the commit I committed this morning did not compile (saw your mail).
>
> Sorry about that. :(
>
> The reason were these PackageHelper changes:
>
>
>
On 06/04/2020 11:48, Alex Dettinger wrote:
a) I think building on top of sinceVersion is good.
b) I don't have strong opinion yet where such information should go.
I don't feel native is the right word, I would tend to see this as a kind
of platform level support like
Yes, the commit I committed this morning did not compile (saw your mail).
Sorry about that. :(
The reason were these PackageHelper changes:
https://github.com/apache/camel/commit/93e11b338ca61415a84c500622ac8f7a2024ce99#diff-e589ec19f41e386bd5611b12566203af
The new commit does not contain
Ah no, it's a different commit this time :-) Sorry for bothering
Il giorno lun 6 apr 2020 alle ore 20:42 Andrea Cosentino
ha scritto:
> This doesn't compile. At least this morning with jdk8
>
> Il lun 6 apr 2020, 20:33 ha scritto:
>
>> This is an automated email from the ASF dual-hosted git
This doesn't compile. At least this morning with jdk8
Il lun 6 apr 2020, 20:33 ha scritto:
> This is an automated email from the ASF dual-hosted git repository.
>
> pascalschumacher pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/camel.git
>
> commit
Hi Zoran,
I have pushed the recent changes to the repository but I have a few
concerns which I have stated on the conversation.
Thank you.
Regards,
Cynthia.
On Sat, Mar 28, 2020 at 2:42 PM Cynthia Omovoiye wrote:
> Hi Zoran,
>
> Please disregard the previous email, I have been able to sort the
Hi
I om okay with a base model have all the potential options across the
different sub projects.
But I dont want the main camel catalog to have data in its catalog
that dont belong there, like the native compilation.
On Mon, Apr 6, 2020 at 4:14 PM Peter Palaga wrote:
>
> On 06/04/2020 14:26,
Sure, will open an issue ticket as I know now it is not intended! ;-)
On 06.04.2020 18:07, Andrea Cosentino wrote:
> Can you provide a reproducer of this?
>
> Il lun 6 apr 2020, 18:04 Benjamin Graf ha scritto:
>
>> Hi Claus,
>>
>> not anymore since commit "CAMEL-14668: camel-core - Optimize
>>
Can you provide a reproducer of this?
Il lun 6 apr 2020, 18:04 Benjamin Graf ha scritto:
> Hi Claus,
>
> not anymore since commit "CAMEL-14668: camel-core - Optimize
> endpoint-dsl for getEndpoint".
>
> NormalizedUri seems to "kill" this feature. Also uris do not have
> schema://... syntax
Hi Claus,
not anymore since commit "CAMEL-14668: camel-core - Optimize
endpoint-dsl for getEndpoint".
NormalizedUri seems to "kill" this feature. Also uris do not have
schema://... syntax anymore. JmsConsumer threads resolving to
JmsConsumer[null]
Regards
Benjamin
On 06.04.2020 17:59, Claus
Hi
It should have string parameters, where you can use {{foo}} as syntax
On Mon, Apr 6, 2020 at 5:19 PM Benjamin Graf wrote:
>
> Hi,
>
> is it intended that endpoint dsl does actually not support property
> placeholder resolving?
>
> Regards,
>
> Benjamin
>
>
--
Claus Ibsen
Hi,
is it intended that endpoint dsl does actually not support property
placeholder resolving?
Regards,
Benjamin
signature.asc
Description: OpenPGP digital signature
Ok, thanks for sharing Peter. Good to know you are on this one :+1 I will
redirect the discussion from
https://github.com/quarkusio/quarkus/issues/2746 to the mailing list.
On Mon, Apr 6, 2020 at 4:17 PM Peter Palaga wrote:
> On 06/04/2020 15:22, Alex Dettinger wrote:
> > Hey Amos,
> >
> >
I’ve been looking at the tables of components, data formats, etc in the website
and wondering if it would be useful to show "version deprecated since” rather
than just the deprecated flag. Is this information even available? Does this
seem like a good idea? I expect to propose a different
On 06/04/2020 15:22, Alex Dettinger wrote:
Hey Amos,
Thanks for input, in such a situation:
+ qute templates would be included anyway independently of
include/exclude patterns
+ resources matching include patterns only would be included
+ except resources matching include and
On 06/04/2020 14:26, Claus Ibsen wrote:
On Mon, Apr 6, 2020 at 11:50 AM Peter Palaga wrote:
Hi,
thanks Claus for writing this down.
On 06/04/2020 09:58, Claus Ibsen wrote:
Hi
Background this PR
https://github.com/apache/camel/pull/3698
a)
I think it can benefit Camel components if we are
Moved down for the moment.
Fixed.
Il giorno lun 6 apr 2020 alle ore 14:20 Claus Ibsen
ha scritto:
> Hi
>
> Yeah that stuff in the top is wrong, it should be moved down to the
> 3.1 to 3.2 section later.
> Another idea is to have a new page per version, then its maybe a bit
> easier to organize
Hi,
The descriptions of components, languages, data formats, etc. in Camel
catalog currently use several inconsistent styles. I wonder whether we
could agree on some common style?
Here an attempt to describe the current state by roughly classifying the
styles and giving some examples. A
Ok, I missed them.
May be we can merge OSGi and Karaf jira components?
regards,
François
fpa...@apache.org
Le 06/04/2020 à 15:33, Jean-Baptiste Onofre a écrit :
> We already have osgi/karaf component in Camel jira.
>
> We can eventually rename it to be "straighter" and more karaf/winegrower
>
We already have osgi/karaf component in Camel jira.
We can eventually rename it to be "straighter" and more karaf/winegrower
generic.
Regards
JB
> Le 6 avr. 2020 à 15:30, Francois Papon a écrit
> :
>
> Hi,
>
> Is there a plan to create a camel-karaf component in Jira?
>
> As Camel-Karaf
Hi,
Is there a plan to create a camel-karaf component in Jira?
As Camel-Karaf has a dedicated git repository, may be it could be easier to
follow related issues.
Thoughts?
regards,
--
François
fpa...@apache.org
Hey Amos,
Thanks for input, in such a situation:
+ qute templates would be included anyway independently of
include/exclude patterns
+ resources matching include patterns only would be included
+ except resources matching include and exclude patterns that would not
be included
So we
Thanks for that. Agree to update the release guide.
Regards
JB
> Le 6 avr. 2020 à 14:36, Andrea Cosentino a
> écrit :
>
> Hello,
>
> As we discussed in the past, I created a tag for the examples
> camel-examples-3.2.0 and updated the master to the newer 3.3.0-SNAPSHOT
>
> We need to add
Hello,
As we discussed in the past, I created a tag for the examples
camel-examples-3.2.0 and updated the master to the newer 3.3.0-SNAPSHOT
We need to add documentation to release guide, to add the steps needed to
create tag for this subproject too.
--
Andrea Cosentino
On Mon, Apr 6, 2020 at 11:50 AM Peter Palaga wrote:
>
> Hi,
>
> thanks Claus for writing this down.
>
> On 06/04/2020 09:58, Claus Ibsen wrote:
> > Hi
> >
> > Background this PR
> > https://github.com/apache/camel/pull/3698
> >
> > a)
> > I think it can benefit Camel components if we are able to
Hi
Yeah that stuff in the top is wrong, it should be moved down to the
3.1 to 3.2 section later.
Another idea is to have a new page per version, then its maybe a bit
easier to organize when we start to have many releases.
On Mon, Apr 6, 2020 at 2:11 PM Pascal Schumacher
wrote:
>
> Hi,
>
>
Hi,
currently the 3.x Upgrade Guide
(https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html) is
confusing, because some information on the 3.2 upgrade is before the 3.1
upgrade while most of it is after the 3.1 upgrade.
In my opinion it would be helpful if the guide was sorted in
I think I've fixed the issues.
David, could you have a look please ?
Le lun. 6 avr. 2020 à 11:58, Guillaume Nodet a écrit :
> I think this is definitely carelessness on my part and I welcome your
> improvements on the doc side, don't get me wrong.
>
> I was working on the first commit since a
Hi Cameleers,
the issue with xref checks running only on the website is that when
the content is restructured it's often that you find out about broken
links after the fact and then one needs to search for the commit that
broke a link.
The idea with the xref checks running in individual
The Camel community announces the immediate availability of Camel,
Camel Spring Boot and Camel Karaf 3.2.0, a new minor release with over
160 new features, improvements and fixes.
Please read our Camel 3.x upgrade guide [1] that describes how to
upgrade Camel 3.1 applications to Camel 3.2.
The
I think this is definitely carelessness on my part and I welcome your
improvements on the doc side, don't get me wrong.
I was working on the first commit since a few weeks, and I think I missed
some changes during the merge phase.
I'll revert the change I made on the
Hi,
thanks Claus for writing this down.
On 06/04/2020 09:58, Claus Ibsen wrote:
Hi
Background this PR
https://github.com/apache/camel/pull/3698
a)
I think it can benefit Camel components if we are able to define what
maturity/stability level the component is (find a good name). For
example
a) I think building on top of sinceVersion is good.
b) I don't have strong opinion yet where such information should go.
I don't feel native is the right word, I would tend to see this as a kind
of platform level support like
On Mon, Apr 6, 2020 at 10:14 AM Omar Al-Safi wrote:
>
> IMO, I'd mark a component as `stable` after a few Camel releases
> that include the component, no idea how many, but this at least gives me
> the hint that the component is stable enough for this use. That means, a
> new component that is
Hello,
For a) I do believe we should use something different from stable, we can
use something like "long-term existence" (thats sounds horrible)
For b) I agree it is something specific to Quarkus for the moment
We need a list of support/maturity/stability levels..
Il giorno lun 6 apr 2020
IMO, I'd mark a component as `stable` after a few Camel releases
that include the component, no idea how many, but this at least gives me
the hint that the component is stable enough for this use. That means, a
new component that is being added to camel code base, I'd mark it as
`Preview`. At
Hi
Background this PR
https://github.com/apache/camel/pull/3698
a)
I think it can benefit Camel components if we are able to define what
maturity/stability level the component is (find a good name). For
example we could the values that other projects uses such as Quarkus
and WildFly: Stable,
The PackageHelper is broken by this commit
Il giorno lun 6 apr 2020 alle ore 09:05 ha
scritto:
> This is an automated email from the ASF dual-hosted git repository.
>
> pascalschumacher pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/camel.git
>
> commit
Wait a moment, we are reverting these changes.
Il giorno lun 6 apr 2020 alle ore 09:18 ha scritto:
> This is an automated email from the ASF dual-hosted git repository.
>
> ramu12 pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/camel-examples.git
>
>
> The
Ramu, please have a look at the git log, we are reverting these changes.
This needs more work to be done.
Il giorno lun 6 apr 2020 alle ore 08:58 ha scritto:
> This is an automated email from the ASF dual-hosted git repository.
>
> ramu12 pushed a commit to branch master
> in repository
Thanks for your participation in this vote.
The vote passes with the following results:
+1 binding: 7 (Alex Dettinger, Andrea Cosentino, Claus Ibsen, Dmitry
Volodin, Gregor Zurowski, Jean-Baptiste Onofré, Luca Burgazzoli)
+1 non-binding: 4 (Đorđe Bajić, François Papon, Federico Valeri, Omar
+1 (binding)
Gregor
On Thu, Apr 2, 2020 at 11:53 AM Gregor Zurowski
wrote:
>
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.2.0 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 160
> improvements and fixes.
>
> Please note that Karaf support has
44 matches
Mail list logo
