I need some help with Spring XSD generation
Hi Cameleers, I've been testing and cherry-picking commits that help with the pipeline build[1] from `jenkins-pipeline` branch to `master`. I was hoping on having a pipeline that would fail as soon as possible by executing in turn build, checks, tests; so we don't wait for the whole build to finish to find out if compile, checkstyle or test fails. Right now I'm stuck on an issue with Spring XSD, that I thought I would workaround by simple `if` in the embedded Ant[2]. This isn't working out. I was hoping that `mvn -Dmaven.test.skip.exec=true clean install` followed by `mvn test` would work, but it fails. Can someone take a look and help me out? Of course simple solution would be to run `install` goal with tests enabled -- I was hoping on avoiding that... Thanks :) zoran [1] https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/ [2] https://github.com/apache/camel/commit/9fbfad95b12a02c94578641798128dfb75fa0b67 -- Zoran Regvart
[GitHub] camel pull request #2239: CAMEL-12293: Avoid KeyAlreadyExistsException for l...
Github user jamesnetherton closed the pull request at: https://github.com/apache/camel/pull/2239 ---
[GitHub] camel pull request #2239: CAMEL-12293: Avoid KeyAlreadyExistsException for l...
GitHub user jamesnetherton opened a pull request: https://github.com/apache/camel/pull/2239 CAMEL-12293: Avoid KeyAlreadyExistsException for listTypeConverters JMX operation https://issues.apache.org/jira/browse/CAMEL-12293 You can merge this pull request into a Git repository by running: $ git pull https://github.com/jamesnetherton/camel CAMEL-12293 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2239.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2239 ---
Re: Getting ready for Apache Camel 2.21 release
On Mon, Feb 26, 2018 at 8:06 PM, Gregor Zurowskiwrote: > Hi, > > Yes, I am available for cutting the release next week. > Thanks, we will keep you updated here on the @dev mailing list. > Thanks, > Gregor > > > On Feb 26, 2018 10:10 AM, "Claus Ibsen" wrote: > > Hi > > We should start to close down and get ready for the expected Camel 2.21 > release. > > If you have any new functionality then its last call to get that > implemented and committed. > > There are currently 61 tickets [1] assigned to 2.21.0 release which is > too much. I will go over them and you are of course also welcome to > take a look, and move tickets to 2.21.1 or 2.22.0. > > I think we need to use this week to get the last tickets resolved, > bugs fixed, stable the CI tests and what else, and then we can touch > base in start of next week to plan for cutting the 2.21 RC builds. > Gregor do you have time for example from next week / next weekend to > cut the RC? > > > [1] - https://issues.apache.org/jira/issues/?jql=project%20% > 3D%20CAMEL%20AND%20fixVersion%20%3D%202.21.0%20AND% > 20statusCategory%20%3D%20new > > > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Getting ready for Apache Camel 2.21 release
Hi Spring Boot 2 is planned for Camel 2.22 release. We would like to work for being able to release Camel 2.22 a bit sooner than usual, maybe around summer. On Mon, Feb 26, 2018 at 2:04 PM, David Karlsenwrote: > It would be super-nice if camel could do a release supporting spring-boot > 2.x quite close to boot 2.x releasing! > > 2018-02-26 10:10 GMT+01:00 Claus Ibsen : > >> Hi >> >> We should start to close down and get ready for the expected Camel 2.21 >> release. >> >> If you have any new functionality then its last call to get that >> implemented and committed. >> >> There are currently 61 tickets [1] assigned to 2.21.0 release which is >> too much. I will go over them and you are of course also welcome to >> take a look, and move tickets to 2.21.1 or 2.22.0. >> >> I think we need to use this week to get the last tickets resolved, >> bugs fixed, stable the CI tests and what else, and then we can touch >> base in start of next week to plan for cutting the 2.21 RC builds. >> Gregor do you have time for example from next week / next weekend to >> cut the RC? >> >> >> [1] - https://issues.apache.org/jira/issues/?jql=project%20% >> 3D%20CAMEL%20AND%20fixVersion%20%3D%202.21.0%20AND% >> 20statusCategory%20%3D%20new >> >> >> >> >> >> -- >> Claus Ibsen >> - >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > > > > -- > -- > David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2