Hi Claus,
Thanks for taking care of this. I will start building the release
candidate now.
Thanks,
Gregor
On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen wrote:
> Hi
>
> I have just pushed fixes for RAT license check and CS checkstyle. They
> all pass now.
> I also added a few missing JARs in th
Hi
I have just pushed fixes for RAT license check and CS checkstyle. They
all pass now.
I also added a few missing JARs in the release kit (the big
zip/tarball with all the JARs)
On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
wrote:
> Hi Everyone,
>
> That is great to hear, I will create the
Hi Alex,
yes indeed, for James Lei's design I would use the JIRA attachment link also:
https://issues.apache.org/jira/secure/attachment/12855173/apachecamel.png
thank you for noticing that :)
zoran
On Fri, Apr 21, 2017 at 5:32 PM, Alex Dettinger wrote:
> Hi Zoran,
>
> Great job. I was a bit
The Apache Jenkins build system has built Camel.trunk.notest (build #3161)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3161/
to view the results.
Hi Zoran,
Great job. I was a bit lost between 1) and 2). Would the proposal below
makes sense ?
1. Design by James Lei submitted at
http://imgur.com/a/Iddxe
2. Design by Bharadwaj Nakka submitted at
https://issues.apache.org/jira/secure/attachment/12856742/new_log_camel.jpg
Cheers,
Alex
On Fr
Hi,
Is there a provision to send url params for the solr url when using solr
component of apache camel? I went through the code on github but couldn't find
anything.
Thanks,
Chirag
From: Chirag Anand
Sent: 21 April 2017 17:29
To: 'dev-subscr...@camel.apache.org'
Subject: FW: Adding Param Opti
I just pushed my Java 9 work and am ready for a release :)
Thanks,
John.
On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
wrote:
> Hi Everyone,
>
> That is great to hear, I will create the release candidate over the
> weekend, if all fixes are available on the master branch.
>
> Thanks,
> Grego
Github user johnpoth closed the pull request at:
https://github.com/apache/camel/pull/1653
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
i am using eclipse personally.
eclipse support in such cases would be nice even though i did not come
across the issue Zoran mentioned.
i have other issues with eclipse :):)
btw, if i could find proper licence i am considering migrating to idea:)
eclipse even helps a lot and cool for recent ride
GitHub user johnpoth opened a pull request:
https://github.com/apache/camel/pull/1653
CAMEL-10141 upgrade to Java 9 build 165
This PR makes more modules unit tests pass on the latest Java 9 build 165
You can merge this pull request into a Git repository by running:
$ git pull h
Hi Everyone,
That is great to hear, I will create the release candidate over the
weekend, if all fixes are available on the master branch.
Thanks,
Gregor
On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart wrote:
> Hi Cameleers,
> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to mast
Hi Cameleers,
Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
thank you :)
zoran
On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen wrote:
> And Zoran has CAMEL-11181 outstanding.
--
Zoran Regvart
Github user zregvart closed the pull request at:
https://github.com/apache/camel/pull/1651
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
Hi
Okay Spring Boot 1.5.3 has been released and we have upgraded to this version.
We are waiting for those java 9 fixes that John will submit later today.
And Zoran has CAMEL-11181 outstanding.
On Fri, Apr 21, 2017 at 10:24 AM, Claus Ibsen wrote:
> Hi
>
> So there is some fixed in the works for
Github user dmvolod closed the pull request at:
https://github.com/apache/camel/pull/1652
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
GitHub user dmvolod opened a pull request:
https://github.com/apache/camel/pull/1652
fixing a small java doc misprint which is propagated to docs and fusetools
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dmvolod/camel docs-mi
The Apache Jenkins build system has built Camel.trunk.notest (build #3160)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3160/
to view the results.
Hi Cameleers,
I would like to post this to the news section of the site and to the
users mailing list:
"
The Camel community had a call for the design of a new logo[1] and we
have received nine design proposals in chronological order:
1. Design by James Lei submitted at
https://issues.apache.org/
Hi Dmitry,
we already have gmavenplus in Salesforce component, I've logged
CAMEL-11181[1] and created a pull request[2], can you help by
reviewing the pull request?
thank you :)
zoran
[1] https://issues.apache.org/jira/browse/CAMEL-11181
[2] https://github.com/apache/camel/pull/1651
On Fri, Apr
GitHub user zregvart opened a pull request:
https://github.com/apache/camel/pull/1651
CAMEL-11181 Replace gmaven with gmavenplus Maven plugin
This replaces the use of `gmaven` plugin with `gmavenplus` plugin.
You can merge this pull request into a Git repository by running:
$ g
Hi Zoran!
Thanks a lot for your tips.
As two latest gmaven plugin usage was introduced by me in camel-protobuf
and camel-grpc components, I'm able to schedule gmaven -> gmavenplus
transition in future components improvement.
--
Best regards,
Dmitry
2017-04-21 12:20 GMT+03:00 Zoran Regvart :
> H
Github user igarashitm closed the pull request at:
https://github.com/apache/camel/pull/1648
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Hi Cameleers,
we are using gmaven plugin in couple of modules, it seems that going
forward it would be better to switch to gmavenplus plugin, well, at
least with Java 9 and Jigsaw[1].
I would like to make that switch, do you think this is something worth
doing, and worth doing in 2.19?
zoran
[1]
Hi Cameleers,
anyone else using _sigh_ Eclipse?
I don't actually think that we need the Eclipse setup in `camel-etc`:
If you have the support in Eclipse, namely: Checkstyle plugin, m2e
with Checkstyle extension (gets auto installed on import) and enable
the `sourcecheck` profile -- then the Check
Hi
I dont use Eclipse but reading this seems to make sense to me.
Anyone using Eclipse can maybe comment on this, how it is to work with
the Camel source code using Eclipse.
The IDEA users dont have any problems, just open the pom.xml files and
you are ready. If you want you can install the chec
Github user dmvolod closed the pull request at:
https://github.com/apache/camel/pull/1650
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Hi
So there is some fixed in the works for making the source build on
Java 9. John will submit a PR later today. We are also waiting for the
Spring Boot 1.5.3 release. They released 1.4.6 yesterday and are
working on the 1.5.x release.
The CI servers should still look good but sometimes they cann
GitHub user dmvolod opened a pull request:
https://github.com/apache/camel/pull/1650
fixing links and misprints inside components docs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dmvolod/camel docs-misprints
Alternatively yo
The Apache Jenkins build system has built Camel.trunk.notest (build #3159)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3159/
to view the results.
Github user jamesnetherton closed the pull request at:
https://github.com/apache/camel/pull/1649
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
The Apache Jenkins build system has built Camel.trunk.notest (build #3158)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3158/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3157)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3157/
to view the results.
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1647
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
33 matches
Mail list logo
