You're right, but if we always think about how much effort is needed to switch
to a new and different JDK, we will never move from JDK 8.
I'd like to have other feedback on this by the way.
For the compatibility matrix we need to it to the documentation too.
--
Andrea Cosentino
Almost +1, (as points below affects the idea of where to using any camel
versions and even contributing because for example;
if you use (let's say JDK 8) and have come across a problem and solved in
your local branch 2.X and submitted and if Camel 3.X would require JDK 10
as the base minimum
Hi,
Thanks Zoran, it is really great effort.
As i did not have experience with Antora and was following up with previous
effort where we used Hugo, webpack & gulp + ascii doctor.
Both approaches seems having trade-offs, i think better one is where we can
do progress as web-site under
Hi,
+1 to website and JDK 11 comptability definitely.
One small note i want to say IMHO, velocity of adoption of new JDK releases
in some corp env is not as fast as JDK releases. I am not saying JDK is
super fast on new deliveries but in corp adoptions are somehow tedious and
not easy.
it would
lburgazzoli opened a new pull request #288: Support for camel context customizer
URL: https://github.com/apache/camel-k/pull/288
Fixes #287
This is an automated message from the Apache Git Service.
To respond to the message,
lburgazzoli opened a new issue #287: Support for camel context customizer
URL: https://github.com/apache/camel-k/issues/287
pre-requisite for #259
This is an automated message from the Apache Git Service.
To respond to the
lburgazzoli opened a new pull request #286: Inject camel-k version as
environment variable
URL: https://github.com/apache/camel-k/pull/286
Fixes #285
This is an automated message from the Apache Git Service.
To respond to
lburgazzoli opened a new issue #284: Platform options
URL: https://github.com/apache/camel-k/issues/284
We do not yet have a way to store platform level / global options so i.e:
- we hard-coded bits such as the camel version to use
- we can configure maven repositories at
lburgazzoli opened a new issue #285: Inject camel-k version as environment
variable
URL: https://github.com/apache/camel-k/issues/285
This is an automated message from the Apache Git Service.
To respond to the message,
Awesome Zoran! Great work!:)
Am 12. Dez. 2018, 19:25 +0100 schrieb David Jencks :
> Hi Zoran,
>
> I don’t quite understand why, how, or where you are setting up symlinks for
> the components. Is there some reason not to put the expected antora directory
> structure inside each components
Hi Zoran,
I don’t quite understand why, how, or where you are setting up symlinks for the
components. Is there some reason not to put the expected antora directory
structure inside each components expected maven directory structure and
assemble them using antora?
e.g.
nicolaferraro opened a new issue #282: Generate website using Antora
URL: https://github.com/apache/camel-k/issues/282
So it can be easily imported in the main Camel website
This is an automated message from the Apache Git
On Wed, Dec 12, 2018 at 3:49 PM Nicola Ferraro wrote:
>
> Yeah, the approach seems good!
>
> I'll start to prepare Camel K to provide documentation in the form Antora
> expects, so we can merge it in the main Camel website. We already have some
> doc pages in the .adoc format, we need to organize
Yeah, the approach seems good!
I'll start to prepare Camel K to provide documentation in the form Antora
expects, so we can merge it in the main Camel website. We already have some
doc pages in the .adoc format, we need to organize them better.
Nicola
On Wed, Dec 12, 2018 at 3:28 PM Andrea
Very well done Zoran, thanks!
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Wednesday, December 12, 2018, 12:10:33 PM GMT+1, Zoran Regvart
Because it was my fault :-D
--Andrea Cosentino --Apache Camel PMC
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail:
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd
On Wednesday, December 12, 2018, 2:43:21 PM GMT+1, Andrea Cosentino
wrote:
Please lets maintain the commits tree clean..
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Wednesday, December 12, 2018, 1:53:22 PM GMT+1,
WildFly-Camel 9.0.0 provides Camel-2.23.0 integration with WildFly-15.0.0
This is a major WildFly upgrade that also comes with a new Camel version. It's
main focus has been on CXF/Elytron integration.
Component upgrades include
WildFly-15.0.0
Camel-2.23.0
Hawtio-2.3.0
In addition to that, we
Thanks!
Regards,
François Papon
fpa...@apache.org
Le 12/12/2018 à 16:12, Zoran Regvart a écrit :
> Hi Francois,
> yes, and with the separate build we can get much faster turnaround on
> the website, I'm just about to push these changes to git and I'll work
> on the build next.
>
> I've pushed
Hi Cameleers,
I've pushed my changes to the `master` of `camel-website`[1], still
really rough, like I mentioned in the previous e-mail I'll work on the
build next and then there will be something to see on the staging site
at https://came.apache.org/staging. I'll post an update when I'm done
with
Hi Francois,
yes, and with the separate build we can get much faster turnaround on
the website, I'm just about to push these changes to git and I'll work
on the build next.
I've pushed Antora based directory changes to the `camel` git
repository's `website` branch[1] few minutes ago.
I'll work
On Wed, Dec 12, 2018 at 1:11 PM Andrea Cosentino wrote:
>
> It makes sense to set a date.
>
> Once we checked the documentation and resolved doubts,
> I propose Wed 19th Dec in the morning.
>
> Does it work for all?
>
+1
> Thanks.
>
> --
> Andrea Cosentino
> --
>
It makes sense to set a date.
Once we checked the documentation and resolved doubts,I propose Wed 19th Dec in
the morning.
Does it work for all?
Thanks.
--Andrea Cosentino --Apache Camel PMC
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail:
On Wed, Dec 12, 2018 at 12:14 PM Guillaume Nodet wrote:
>
> Sounds good to me.
>
> Fwiw, I've been working on the camel build those past days, trying to
> improve things a bit. I'll report when I have something in a correct shape.
>
What if we set a date when we make the change? For example
Hi,
Good point for the camel-website repository :)
May be it could be interesting to have 2 jobs on Jenkins for the
website: master and PR. This jobs could build and published on online
demo site.
Thoughts ?
Regards,
François Papon
fpa...@apache.org
Le 12/12/2018 à 15:10, Zoran Regvart a
Sounds good to me.
Fwiw, I've been working on the camel build those past days, trying to
improve things a bit. I'll report when I have something in a correct shape.
Guillaume
Le mer. 12 déc. 2018 à 11:54, Andrea Cosentino
a écrit :
> Hello,
>
> Since we started work of some cleanup about
Hi Cameleers,
I've found some time to work on the website and here's the current
status on the progress we made.
We had some great contributions on the new website raging from the
Asciidoctor theme and build for the user manual that Francois
contributed, to the wiki pages migration that Alex,
Hello,
Since we started work of some cleanup about Camel 3 and it's already aligned
with master, I'd like to ask what do you think about switching the master to
3.x and create a 2.x branch for the activities on Camel 2.x..
What do you think about this?
Thanks
--
Andrea Cosentino
lburgazzoli closed pull request #281: chore(dev) make dev mode 10x faster on
remote clusters by caching client
URL: https://github.com/apache/camel-k/pull/281
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
29 matches
Mail list logo
