On Thu, Aug 20, 2009 at 3:43 PM, Christian Schneider<ch...@die-schneider.net> wrote: > Hi Hadrian and Claus, > > I have created a ticket https://issues.apache.org/activemq/browse/CAMEL-1924 > and attached all necessary mails from this thread. >
Thanks a lot I guess most of these is easy to fix. If you have time patches is also much welcome as you got the windows system. Otherwise we gotta wait for the CI servers to do a run and test on the windows boxes :) > btw: You guys did some great work with the new camel release. We are already > using the 2.0.0-M3 in production and looking forward to the final 2.0.0. > Glad to know its already in production. You are not the first on a Mx in production but glad it works for you. > Greetings > > Christian > > > Hadrian Zbarcea schrieb: >> >> Awesome work Christian, thank you for the extra effort. As Claus said, >> we'll get this fixed as soon as 2.0 is out the door. >> >> Cheers, >> Hadrian >> >> On Aug 20, 2009, at 8:25 AM, Claus Ibsen wrote: >> >>> On Thu, Aug 20, 2009 at 2:22 PM, Christian >>> Schneider<ch...@die-schneider.net> wrote: >>>> >>>> Hi Hadrian, >>>> >>>> I have just debugged the last failure: >>>> >>>> org.apache.camel.processor.ChoiceWithEndTest.testRouteIsCorrectAtRuntime >>>> >>>> It checks for 4 nodes but only gets one. >>>> >>>> The reason is that it checks the wrong route. When I change the line >>>> Navigate<Processor> nav = context.getRoutes().get(0).navigate(); >>>> to >>>> Navigate<Processor> nav = context.getRoutes().get(1).navigate(); >>>> then it works. So it seems the sequence of the routes is not the same >>>> for >>>> all systems. Perhaps it would be better to use another way of getting >>>> the >>>> route from the camel context. >>>> >>>> So after I have checked all the failures I would also say there is no >>>> blocker. >>>> Should I create jira tickets for the three problems? >>> >>> Just create one ticket as the issue are minor. We will get it fixed >>> post 2.0 release. >>> >>> >>>> >>>> Greetings >>>> >>>> Christian >>>> >>>> Hadrian Zbarcea schrieb: >>>>> >>>>> Hi Christian, >>>>> >>>>> Thanks for doing the tests. No, it is not ok, but all the tests are >>>>> passing consistently for a few weeks on mac and linux. That code is >>>>> not >>>>> quite platform specific (well, except for the Windows fs). Could you >>>>> *please* take a look a bit more and maybe figure out what the issue is? >>>>> Is >>>>> it a fluke, a timing issue, a more serious problem, does it work from >>>>> an IDE >>>>> like Eclipse? >>>>> >>>>> Imho this is not a blocker for this release (yet), but it's good to >>>>> know. >>>>> >>>>> Many thanks again, >>>>> Hadrian >>>>> >>>>> >>>>> On Aug 19, 2009, at 7:26 AM, Christian Schneider wrote: >>>>> >>>>>> I just checked out the head (hope this is still the release 2.0.0 >>>>>> state) >>>>>> and did a full build. I got three test failures in camel-core. Is this >>>>>> ok? >>>>>> >>>>>> I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0. >>>>>> >>>>>> Greetings >>>>>> >>>>>> Christian >>>>>> Failure Details >>>>>> >>>>>> <icon_warning_sml.gif> testCannotDeleteFile >>>>>> >>>>>> junit.framework.AssertionFailedError: Should have thrown an exception >>>>>> >>>>>> >>>>>> >>>>>> org.apache.camel.component.file.strategy.GenericFileDeleteProcessStrategyTest:125 >>>>>> <icon_warning_sml.gif> testCacheStreamToFileAndNotCloseStream >>>>>> >>>>>> junit.framework.AssertionFailedError: we should have no temp file >>>>>> expected:<1> but was:<0> >>>>>> >>>>>> org.apache.camel.converter.stream.CachedOutputStreamTest:117 >>>>>> <icon_warning_sml.gif> testRouteIsCorrectAtRuntime >>>>>> >>>>>> junit.framework.AssertionFailedError: expected:<4> but was:<1> >>>>>> >>>>>> org.apache.camel.processor.ChoiceWithEndTest:39 >>>>>> >>>>>> >>>>>> Hadrian Zbarcea schrieb: >>>>>>> >>>>>>> The first release candidate of apache-camel-2.0.0 is out with 61 new >>>>>>> features, improvements and bug fixes. This concludes more than one >>>>>>> year of >>>>>>> efforts to bring a new and improved Apache Camel. Many thanks to >>>>>>> everybody >>>>>>> in the community who contributed to this release. >>>>>>> >>>>>>> Please find the staging repo here: >>>>>>> >>>>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/ >>>>>>> >>>>>>> The tarballs are here >>>>>>> >>>>>>> >>>>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/ >>>>>>> >>>>>>> Please vote to approve this release binary >>>>>>> >>>>>>> [ ] +1 Release the binary as Apache Camel 2.0-M3 >>>>>>> [ ] -1 Veto the release (provide specific comments) >>>>>>> Vote is open for 72 hours. >>>>>>> >>>>>>> >>>>>>> The Camel Riders >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> -- >>> Claus Ibsen >>> Apache Camel Committer >>> >>> Open Source Integration: http://fusesource.com >>> Blog: http://davsclaus.blogspot.com/ >>> Twitter: http://twitter.com/davsclaus >> >> > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
