[GitHub] camel pull request #1998: Skip FileWatcherReloadStrategyTest on windows as a...

Github user PascalSchumacher closed the pull request at: https://github.com/apache/camel/pull/1998 ---

[GitHub] camel pull request #2086: CAMEL-11954: Renamed HA packages to cluster

GitHub user vrlgohel opened a pull request: https://github.com/apache/camel/pull/2086 CAMEL-11954: Renamed HA packages to cluster Fix for issue: https://issues.apache.org/jira/browse/CAMEL-11954 Refactored 'ha' packages to cluster' in camel-core as well as other associated compo

Re: Next round of patch releases - Camel 2.19.4 and 2.20.1

Hi Gregor CXF has been upgraded, so the 2.20.x branch should be ready for the RC On Mon, Nov 6, 2017 at 9:50 AM, Claus Ibsen wrote: > Hi Gregor > > Its almost ready. There is a new CXF 3.2.1 release on the way (in vote > now). It would be good IMHO to upgrade to this version. > > http://cxf.5472

[GitHub] camel pull request #2085: CAMEL-11995: Salesforce Composite API support

GitHub user zregvart opened a pull request: https://github.com/apache/camel/pull/2085 CAMEL-11995: Salesforce Composite API support Adds support for third Composite resource, now we can support Batch, Tree and plain "Composite" resource. Composite resource allows generating a

[GitHub] camel pull request #2084: Fix tests in camel-cdi

Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/2084 ---

Re: Maven memory issues on Jenkins

Hi Gregor, awesome! I think you can use the Jenkinsfile from my fork[1] as a starting point. Looking at it I remembered that I wanted to have Java 8/9 build run in parallel, and that complicates the build as two checkouts are needed (for two nodes). If you'd like to start from a fresh, that's also

[GitHub] camel pull request #2084: Fix tests in camel-cdi

GitHub user johnpoth opened a pull request: https://github.com/apache/camel/pull/2084 Fix tests in camel-cdi This was caused by [CAMEL-11822](https://issues.apache.org/jira/browse/CAMEL-11822). Looks like jaxb 2.3.0 is stricter with namespace declarations. Tested on Java 9 GA as we

[GitHub] camel pull request #2083: Add Maven Wrapper

GitHub user gzurowski opened a pull request: https://github.com/apache/camel/pull/2083 Add Maven Wrapper As discussed in http://camel.465427.n5.nabble.com/Maven-memory-issues-on-Jenkins-td5815273.html You can merge this pull request into a Git repository by running: $ git pull

Re: Maven memory issues on Jenkins

Hi Zoran, It would be great if we could switch to the Jenkinsfile approach soon. I'd be available to help with this. :) Thanks, Gregor On Tue, Nov 7, 2017 at 10:16 AM, Zoran Regvart wrote: > Hi Gregor & Cameleers, > yeah I think we should add Maven Wrapper, I think it's good to have as > much

Re: Maven memory issues on Jenkins

I have created a PR for the Maven wrapper [1] targeting the master branch and using Maven 3.5.2. Thanks, Gregor [1] https://github.com/apache/camel/pull/2083 On Tue, Nov 7, 2017 at 10:16 AM, Zoran Regvart wrote: > Hi Gregor & Cameleers, > yeah I think we should add Maven Wrapper, I think it's

Re: Maven memory issues on Jenkins

Hi Gregor & Cameleers, yeah I think we should add Maven Wrapper, I think it's good to have as much project related tools/scripts within source control. Some time ago I started experimenting on how to make the build faster on Jenkins and I created a branch[1] to experiment with on my GitHub fork. I

Re: Maven memory issues on Jenkins

Hi Zoran, Thanks for digging into this. What do you think about using the Maven Wrapper for Camel going forward? This way we could manage the Maven version from within the project itself and even use the correct Maven version per branch / Camel release (via the maven-wrapper.properties file). T